[Feature Flag] Cleanup api_kaminari_count_with_limit
Summary
This issue is to cleanup the api_kaminari_count_with_limit
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
The feature flag is enabled globally as we can see running: /chatops run feature get api_kaminari_count_with_limit
.
This is an old feature flag, introduced in 11.8 with gitlab-foss!23931 (merged) and the last time someone looked at was !43428 (merged).
-
Default enabled. !82003 (merged) (%14.9) -
Cleanup feature flag. !81084 (merged) (>= %14.10)
Related discussion #352597 (comment 840133891).
Owners
- Team: ~"group::integrations"
- Most appropriate slack channel to reach out to:
#g_ecosystem_integrations
- Best individual to reach out to: @rymai + @gitlab-org/ecosystem-stage/integrations
- PM: @g.hickman
Stakeholders
Expectations
What might happen if this goes wrong?
Cleaning up the feature flag
-
Create a merge request to remove api_kaminari_count_with_limit
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
/chatops run auto_deploy status <merge-commit-of-cleanup-mr>
-
-
Close the feature issue to indicate the feature will be released in the current milestone. -
Clean up the feature flag from all environments by running these chatops command in #production
channel:-
/chatops run feature delete api_kaminari_count_with_limit --dev
-
/chatops run feature delete api_kaminari_count_with_limit --staging
-
/chatops run feature delete api_kaminari_count_with_limit
-
-
Close this rollout issue.
Edited by Andy Schoenen