[Feature flag] Cleanup ci_enforce_throttle_pipelines_creation

Summary

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

Owners

• Team: grouppipeline execution
• Most appropriate slack channel to reach out to: #g_pipeline-execution
• Best individual to reach out to: @mbobin
• PM: @jheimbuck_gl

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

• Enable ci_enforce_throttle_pipeline_creation by default with chatops for GitLab.com -> ✅
• Enable ci_enforce_throttle_pipeline_creation by default for SM enabled: true in the yml file) -> 18.3 ✅
• Create a merge request to remove ci_enforce_throttle_pipeline_creation feature flag. -> 18.4
  • 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.