[Feature flag] Cleanup compressed_package_metadata_query
Summary
This issue is to cleanup the compressed_package_metadata_query feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
See the following for more details:
- [Feature flag] Rollout of `compressed_package_m... (#409793 - closed)
- Update package metadata license lookup to use d... (#408906 - closed)
Owners
- Team: Composition Analysis
- Most appropriate slack channel to reach out to:
#g_secure-composition-analysis - Best individual to reach out to: @adamcohen
- PM: @smeadzinger
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 compressed_package_metadata_query flag (!130976 - 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. -
Remove the projectparameter from Gitlab::LicenseScanning::PackageLicenses#initialize since theprojectparameter only exists to determine whether thecompressed_package_metadata_queryfeature flag has been enabled on the project. See this discussion for more details.
-
-
-
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. -
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 #productionchannel:-
/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 Adam Cohen

