[Feature flag] Cleanup project_templates_without_min_access

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

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

Related:

• Add a feature flag around the code with poor pe... (!132025 - merged)
• [Feature flag] Rollout of `project_templates_wi... (#480779 - closed)
• [Feature flag] Rollout of `project_templates_wi... (#425452)
• Investigate other solutions to the performance ... (#441462 - closed)

Owners

• Team: Source Code
• Most appropriate slack channel to reach out to: #g_create_source-code
• Best individual to reach out to: @vyaklushin, @ashmckenzie
• PM: @derekferguson, @mcbabin, @dpoosarla

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 project_templates_without_min_access 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 project_templates_without_min_access --dev --pre --staging --staging-ref --production
• Close this rollout issue.