[Feature flag] Cleanup gtm_nonce
Summary
This issue is to cleanup the gtm_nonce
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
Primary issue: gitlab-com/marketing/digital-experience&42 (closed) Rollout issue: #346322 (closed)
Owners
- Team: groupacquisition
- Most appropriate slack channel to reach out to:
#g_acquIsition
- Best individual to reach out to: @laurenbarker
- PM: @gdoud
Stakeholders
Expectations
What might happen if this goes wrong?
Cleaning up the feature flag
-
Create a merge request to remove gtm_nonce
feature flag. Ask for review and merge it. - !133463 (merged)-
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 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133463
-
-
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 gtm_nonce --dev --staging --staging-ref --production
-
-
Close this rollout issue.
Edited by Doug Stull