[Feature flag] Cleanup descendant_security_scans
Summary
This issue is to cleanup the descendant_security_scans
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
Owners
- Team: Threat Insights
- Most appropriate slack channel to reach out to:
#g_govern_threat_insights
- Best individual to reach out to:
@mokhax
- PM:
@abellucci
Stakeholders
Expectations
What might happen if this goes wrong?
Cleaning up the feature flag
-
Create a merge request to remove descendant_security_scans
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 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/130217
result
-
-
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: -
Close this rollout issue.
Edited by mo khan