Repositories storage settings: separate `hg_path` configuration item
In v16.7.0, upstream is removing the path
item of repositories storages in gitlab.yml
, see !657 (merged) and specifically fdc65519a614.
They are actually keeping it as a non mandatory option that can be read only once (replaced then by a deprecation marker). As our repository classes still need it, this breaks a few tests and makes it hard to be sure it can be safely used (never read again) in production.
At this point, we could finish %HGitaly3: fully in charge and do without any knowledge of local paths, the HGitaly server being potentially remote, but doing so for %Heptapod 1.1 would be rushing it and brings too much risk. It is on the other hand reasonable, perhaps with feature flags in the GitLab 17 timeline (May 2024).
Instead, we will use a new hg_path
item that will support our transition to potentially remote HGitaly. We have checked as far as GitLab v16.8.0 that the storage
item will still be a mapping.
This is a breaking change for source installations, Omnibus and therefore Docker installations should not need a change in their higher level configuration.