[Feature flag] Cleanup ci_job_jwt
Summary
This issue is to cleanup the ci_job_jwt
feature flag, which has been enabled since before %13.0
Owners
- Team: grouppipeline authoring
- Most appropriate slack channel to reach out to:
#g_pipeline_authoring
- Best individual to reach out to: @avielle
- PM: @dhershkovitch
Expectations
What might happen if this goes wrong?
If a self-managed instance has manually disabled this flag, their jobs will now have JWT tokens defined
Cleaning up the feature flag
-
Create a merge request to remove ci_job_jwt
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 ci_job_jwt --dev
-
/chatops run feature delete ci_job_jwt --staging
-
/chatops run feature delete ci_job_jwt
-
-
Close this rollout issue.
Edited by Avielle Wolfe