Deprecate Legacy storage for GitLab generally (not just Geo)
The vision
~Geo is quickly moving ahead with requiring hashed storage.
- We've done all the work to deprecate legacy storage just for Geo: https://gitlab.com/gitlab-org/gitlab-ee/issues/8289
- And now we just need to include the deprecation notice in all release posts until 12.0: gitlab-com/www-gitlab-com#3508 (closed)
- And in 12.0 we will enforce hashed storage programmatically: https://gitlab.com/gitlab-org/gitlab-ee/issues/8690
This issue is intended to track the effort to require hashed storage for any GitLab installation.
- This is valuable because e.g. renames and transfers are very fragile, and are much more robust with hashed storage
- This is safe after we dogfood hashed storage on GitLab.com
- Eventually we could delete legacy pathways and the hashed storage setting
To Do
-
Enable the setting by default in development https://gitlab.com/gitlab-org/gitlab-ce/issues/46241 -
Deprecate Legacy storage only for ~Geo https://gitlab.com/gitlab-org/gitlab-ee/issues/8289 -
[In progress in separate issue] Migrate all projects on GitLab.com to Hashed storage https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/4772 -
Enable "Use hashed storage paths for newly created and renamed projects" by default for new installations -
Move the Hashed storage checks to gitlab:app:check
task instead ofgitlab:geo:check
-
Add deprecation notice in release post -
Open an issue to enable it on existing installations in next major release
Labeling with ~Geo because ~Geo owns Hashed storage. But this issue specifically applies to GitLab generally.
Edited by Rachel Nienaber