Deprecate non-hashed repository storage for Geo installations
What does this MR do?
Add hashed storage checks to Geo check task. As the first step in deprecating legacy storage.
Screenshots
When hashed storage is disabled
When hashed storage is enabled but a project exists in legacy storage
When hashed storage is enabled and all projects are in hashed storage
What are the relevant issue numbers?
https://gitlab.com/gitlab-org/gitlab-ee/issues/8289 (does not close because we also need flash warnings, which are being added in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8433).
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
Tests added for this feature/bug -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
EE specific content should be in the top level /ee
folder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan? -
Security reports checked/validated by reviewer
Edited by Michael Kozono