Delete the `zoekt_cache_search_responses` feature flag
Delete the zoekt_cache_search_responses feature flag
This feature flag was introduced in 16.7, which is more than 12 milestones ago.
As part of our process we want to ensure feature flags don't stay too long in the codebase.
Rollout issue: (missing URL)
Remaining mentions of the feature flag (click to expand)
changelogs/archive-16.md
1222:- [Rollout zoekt_cache_search_responses feature](gitlab-org/gitlab@49d4a9163ba4a9e2b65ddfefc61c100532ce61b0) ([merge request](gitlab-org/gitlab!146085)) **GitLab Enterprise Edition**
Currently the feature flag is enabled on production
It is possible that this MR will still need some changes to remove references to the feature flag in the code.
At the moment the gitlab-housekeeper is not always capable of removing all references so you must check the diff and pipeline failures to confirm if there are any issues.
It is the responsibility of groupglobal search to push those changes to this branch.
If they are already removing this feature flag in another merge request then they can just close this merge request.
TODO for the reviewers before merging this MR
-
See the status of the rollout by checking (missing URL), https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/-/issues/?search=zoekt_cache_search_responses&sort=created_date&state=all&label_name%5B%5D=host%3A%3Agitlab.com -
Verify the feature flag status via chatops by running /chatops run feature get zoekt_cache_search_responses. -
Search for references to ZoektCacheSearchResponsesin frontnd part of code -
Search for references to zoekt_cache_search_responsesin code -
Check if we need to remove any Gem or other related code by looking at the changes in !137337 (merged)
This change was generated by gitlab-housekeeper using the Keeps::DeleteOldFeatureFlags keep.
To provide feedback on your experience with gitlab-housekeeper please create an issue with the
label GitLab Housekeeper and consider pinging the author of this keep.
Changelog: removed