Skip to content
Snippets Groups Projects

Update documentation to match Gitaly's new configuration structure

Merged Sami Hiltunen requested to merge smh-update-gitaly-config-structure into master
All threads resolved!
+ 14
2
@@ -280,7 +280,13 @@ and [Helm Chart deployments](https://docs.gitlab.com/charts/). They come with ap
the repository using `praefect remove-repository` to remove the repository's remaining records.
You can find repositories with invalid metadata records prior in GitLab 15.0 and later by searching for the log records outputted by the verifier. You can find an example log record [here](../administration/gitaly/praefect.md#repository-verification).
- Praefect's configuration structure in Omnibus GitLab [has been changed](https://gitlab.com/gitlab-org/gitaly/-/issues/4467) to be consistent Praefect's own configuration structure used in source installs. Praefect's configuration is now under `praefect['configuration']` as a single hash. There are still other top-level keys in `praefect` used by Omnibus. Migrate by moving the configuration under the new structure. Below is the new structure with the old keys described in a comment above the key. Replace the `...` with the value from the old key. Default values are the same. If you haven't configured a value previously, you don't have to configure it now either. Remove the old keys from the configuration once migrated.
- Praefect configuration structure in Omnibus GitLab [has changed](https://gitlab.com/gitlab-org/gitaly/-/issues/4467) to be consistent with the Praefect configuration structure
used in source installs. Praefect configuration is now under `praefect['configuration']` as a single hash. There are still other top-level keys in `praefect` used by
Omnibus GitLab.
Migrate by moving your existing configuration under the new structure. Below is the new structure with the old keys described in a comment above the key. Replace the
`...` with the value from the old key. Default values are the same. If you haven't configured a value previously, you don't need to configure it. Remove the old keys
from the configuration once migrated.
```ruby
praefect['configuration'] = {
@@ -407,7 +413,13 @@ and [Helm Chart deployments](https://docs.gitlab.com/charts/). They come with ap
}
```
- Gitaly's configuration structure in Omnibus GitLab [has been changed](https://gitlab.com/gitlab-org/gitaly/-/issues/4467) to be consistent Gitaly's own configuration structure used in source installs. Gitaly's configuration is now under `gitaly['configuration']` as a single hash. There are still other top-level keys in `gitaly` used by Omnibus. Migrate by moving the configuration under the new structure. Below is the new structure with the old keys described in a comment above the key. Replace the `...` with the value from the old key. Default values are the same. If you haven't configured a value previously, you don't have to configure it now either. Remove the old keys from the configuration once migrated.
- Gitaly configuration structure in Omnibus GitLab [has changed](https://gitlab.com/gitlab-org/gitaly/-/issues/4467) to be consistent with the Gitaly configuration structure
used in source installs. Gitaly configuration is now under `gitaly['configuration']` as a single hash. There are still other top-level keys in `gitaly` used by
Omnibus GitLab.
Migrate by moving your existing configuration under the new structure. Below is the new structure with the old keys described in a comment above the key. Replace the
`...` with the value from the old key. Default values are the same. If you haven't configured a value previously, you don't need to configure it. Remove the old keys
from the configuration once migrated.
```ruby
gitaly['configuration'] = {
Loading