[Feature flag] Cleanup track_geo_proxy_events
Summary
This issue is to cleanup the track_geo_proxy_events
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
This should be removed after confirming service ping data includes the new Geo events, approximately one milestone after %14.7 where this was enabled by default.
Owners
- Team: groupgeo
- Most appropriate slack channel to reach out to:
#g_geo
- Best individual to reach out to:
@cat
- PM:
@nhxnguyen
Stakeholders
Expectations
What might happen if this goes wrong?
No metrics in the service ping data related to Geo.
Increased number of errors in #show
actions, Redis saturation possibly? (technically not expecting either, but possible side effects)
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. -
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.
Edited by Catalin Irimie