Remove design_management_require_hashed_storage feature flag
:design_management_require_hashed_storage feature flag.
This feature flag was added in #13428 (comment 238729038).
In adding the new requirement for design management that the project repository uses hashed storage #13428 (closed), we were unable to know for certain whether existing customers would be negatively impacted.
As mentioned #13428 (comment 238729038) we decided to couple the hashed storage requirement with a feature flag, enabled by default, so we or other people could re-enable design management if they had legacy storage and found their designs disappear:
I figure this feature flag will be enabled by default and we'll ship the feature flag and leave it for a couple of releases. If we don't hear that anyone was disrupted by the change, we can remove the feature flag. If people were disrupted by the change they can toggle the feature flag to re-enable design management and we can work out what to do from there (either support them in their migration to hashed storage, or come up with a plan B).
- Team: group::knowledge
- Most appropriate slack channel to reach out to:
- Best individual to reach out to: @.luke
### What are we expecting to happen?
Nothing, as the feature flag is enabled by default.
What might happen if this goes wrong?
There is the potential for on-prem customers who had not previously upgraded to 12.5 when the hashed storage was required discovering they are negatively affected once this feature flag is removed.
What can we monitor to detect problems with this?
No monitoring required.
We won't be doing beta testing, as the feature flag has been enabled by default.
Roll Out Steps
- [-] Enable on staging
- [-] Test on staging
- [-] Ensure that documentation has been updated
- [-] Enable on GitLab.com for individual groups/projects listed above and verify behaviour
- [-] Coordinate a time to enable the flag with
- [-] Announce on the issue an estimated time this will be enabled on GitLab.com
- [-] Enable on GitLab.com by running chatops command in
- [-] Cross post chatops slack command to
#support_gitlab-comand in your team channel
- [-] Announce on the issue that the flag has been enabled
- Remove feature flag
After the flag removal is deployed, clean up the feature flag by running chatops command in