Skip to content

[Feature flag] Cleanup manage_compliance_frameworks_modals_refactor

Summary

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

Feature flag will be removed in [Feature flag] Cleanup manage_compliance_framew... (!119581 - merged)

Owners

  • Team: Compliance team
  • Most appropriate slack channel to reach out to: #g_govern_compliance
  • Best individual to reach out to: @elwyn-gitlab
  • PM: @derekferguson

Stakeholders

Expectations

What might happen if this goes wrong?

No DB changes, safe to revert / rollback

Cleaning up the feature flag

  • Create a merge request to remove manage_compliance_frameworks_modals_refactor 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 manage_compliance_frameworks_modals_refactor --dev
    • /chatops run feature delete manage_compliance_frameworks_modals_refactor --staging
    • /chatops run feature delete manage_compliance_frameworks_modals_refactor
  • Close this rollout issue.
Edited by Elwyn Benson