[Feature flag] Cleanup usage_data_incident_management_incident_published
Summary
This issue is to cleanup the usage_data_incident_management_incident_published
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
This was discussed in gitlab-org/quality/triage-reports#13508 (comment 1509064017). Summary:
- The feature has been tested and verified on production in #233933 (comment 413987891)
✅ - This feature flag was added enabled by default since %13.4 without known issues
Owners
- Team: grouprespond
- Most appropriate slack channel to reach out to:
#g_respond
- Best individual to reach out to: @splattael
- PM: @kbychu
Stakeholders
Expectations
What might happen if this goes wrong?
Cleaning up the feature flag
-
Create a merge request to remove <feature-flag-name>
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. -
If not already done, clean up the feature flag from all environments by running these chatops command in #production
channel:-
/chatops run feature delete <feature-flag-name> --dev
-
/chatops run feature delete <feature-flag-name> --staging
-
/chatops run feature delete <feature-flag-name>
-
-
Close this rollout issue.