[Feature flag] Cleanup ensure_pipeline_policy_pre_stage_complete

Summary

This issue is to cleanup the ensure_pipeline_policy_pre_stage_complete and ensure_pipeline_policy_pre_stage_complete_group feature flags, after the feature flags have been enabled by default for an appropriate amount of time in production. The feature is about ensuring that .pipeline-policy-pre stage finishes before any other jobs can start. The feature will be productized.

Owners

• Team: Security Policies
• Most appropriate slack channel to reach out to: #g_srm_security_policies
• Best individual to reach out to: @mcavoj
• PM: @g.hickman

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

• Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup
• Create a merge request to remove ensure_pipeline_policy_pre_stage_complete 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 ensure_pipeline_policy_pre_stage_complete --dev --pre --staging --staging-ref --production
• Close this rollout issue.