Update documentation to match Gitaly's new configuration structure
All threads resolved!
All threads resolved!
Compare changes
Files
13- Sami Hiltunen authored
Omnibus previously had a custom configuration structure for Gitaly that didn't match the actual structure of Gitaly. This made a number of things more difficult than they had to be. Omnibus was recently updated to place Gitaly's configuration under gitaly['configuration'] hash which gets directly marshaled as TOML for the final Gitaly configuration. While there is still backwards compatibility handling in place, we should update the documentation to use the new structure in preparation for deprecating the old configuration keys. This commit updates Gitaly's documentation to refer to the new keys.
@@ -143,7 +143,13 @@ Gitaly and GitLab use two shared secrets for authentication:
@@ -230,14 +236,21 @@ Updates to example must be made at:
@@ -247,24 +260,33 @@ Updates to example must be made at:
@@ -461,17 +483,28 @@ example:
@@ -600,16 +633,21 @@ To configure Gitaly with TLS:
@@ -733,9 +771,16 @@ settings:
@@ -775,21 +820,23 @@ example:
@@ -864,40 +911,47 @@ When these limits are reached, performance may be reduced and users may be disco
@@ -968,10 +1022,16 @@ Make sure to schedule this during off-peak hours and keep the duration short (fo
@@ -1018,7 +1078,13 @@ transitioning" mode as follows:
@@ -1038,8 +1104,13 @@ To update to a new Gitaly authentication token, on each Gitaly client **and** Gi
@@ -1069,7 +1140,13 @@ your Gitaly servers as follows:
@@ -1147,9 +1224,15 @@ setting is discussed in greater detail below.
@@ -1315,7 +1398,32 @@ process repositories that do not pass consistency checks.
@@ -1423,7 +1531,13 @@ proposed in issue [19185](https://gitlab.com/gitlab-org/gitlab/-/issues/19185).