[Feature flag] Cleanup of `merge_sbom_api`

Summary

This issue is to cleanup the merge_sbom_api feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.

Owners

• Team: composition analysis
• Most appropriate slack channel to reach out to: #g_secure-composition-analysis
• Best individual to reach out to: @atiwari71
• EM: @gonzoyumo
• 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 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 <feature-flag-name> --dev
  • /chatops run feature delete <feature-flag-name> --staging
  • /chatops run feature delete <feature-flag-name>
• Close this rollout issue.

changed milestone to %16.5

added feature flag maintenanceremoval typemaintenance labels

assigned to @atiwari71

added groupcomposition analysis label and removed feature flag label

added devopssecure sectionsec labels

added feature flag label and removed devopssecure sectionsec labels

added devopssecure sectionsec labels

mentioned in issue #421513 (closed)

added Category:Software Composition Analysis Enterprise Edition GitLab Ultimate SCA:License Scanning backend labels

added Deliverable label

added workflowrefinement label

marked #425124 (closed) as a duplicate of this issue

marked this issue as related to #425124 (closed)

Setting health status to on track as the milestone has just begun.

Issue participants are welcome to override this by setting the health status to another value.

changed health status to on track

marked this issue as blocked by #421513 (closed)

This issue is scheduled for completion in this milestone but is not yet in development. Changing health status to 'needs attention'.

Issue participants are welcome to override this by setting the health status to another value.

changed health status to needs attention

added workflowin dev label and removed workflowrefinement label

mentioned in merge request !133724 (merged)