[FF] `cells_claims_verification_worker_project` --
## Summary This issue is to roll out [the feature](https://gitlab.com/gitlab-com/gl-infra/tenant-scale/cells-infrastructure/team/-/work_items/468) on production, that is currently behind the `cells_claims_verification_worker_project` feature flag. ## Owners - Most appropriate Slack channel to reach out to: `#g_cells_infrastructure` - Best individual to reach out to: @marcogreg ## Expectations ### What are we expecting to happen? <!-- Describe the expected outcome when rolling out this feature --> ### What can go wrong and how would we detect it? <!-- Data loss, broken pages, stability/availability impact? --> ## Rollout Steps ### Rollout on non-production environments - [ ] Enable the feature globally on non-production environments with `/chatops run feature set cells_claims_verification_worker_project true --dev --pre --staging --staging-ref` - [ ] Verify that the feature works as expected. ### Global rollout on production - [ ] [Incrementally roll out](https://docs.gitlab.com/development/feature_flags/controls/#process) the feature on production. - [ ] After the feature has been 100% enabled, wait for at least one day before releasing the feature. ### Release the feature - [ ] Create a merge request to remove the `cells_claims_verification_worker_project` feature flag. - [ ] Once the cleanup MR has been deployed, delete the flag: `/chatops run feature delete cells_claims_verification_worker_project --dev --pre --staging --staging-ref --production` - [ ] Close this rollout issue. ## Rollback Steps - [ ] `/chatops run feature set cells_claims_verification_worker_project false` - [ ] `/chatops run feature delete cells_claims_verification_worker_project --dev --pre --staging --staging-ref --production`
issue