Related to #7237 and !241926. ## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/issues/7237) currently behind the `deleting_account_disabled_for_enterprise_users` feature flag. - DRI: @habdul-razak - Team Slack channel: `#g_authentication` > [!note] > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? Low risk. The flag is actor-scoped to the enterprise group, defaults off, and only affects enterprise users on GitLab.com Premium groups with domain verification. Non-enterprise users are unaffected. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_authentication`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set deleting_account_disabled_for_enterprise_users 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set deleting_account_disabled_for_enterprise_users true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set deleting_account_disabled_for_enterprise_users <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --group=gitlab-org,gitlab-com deleting_account_disabled_for_enterprise_users true /chatops gitlab run feature set --user=habdul-razak deleting_account_disabled_for_enterprise_users true ``` ## Monitoring 24h soak at 100% before cleanup. The flag is evaluated in page renders and a destroy action, not in background jobs. - [`web` service overview](https://dashboards.gitlab.net/d/web-main/web-overview) — Apdex or error-ratio dip starting at the ChatOps annotation marker. - [`web` Rails controller](https://dashboards.gitlab.net/d/web-rails-controller/web-rails-controller) — latency or SQL-time increase on `Profiles::AccountsController`, `RegistrationsController#destroy`, `groups#update`. More sensitive than the service graph. - [Sentry](https://new-sentry.gitlab.net) — exceptions in `ProfilesHelper#prevent_delete_account?` or `EE::Group#prevent_enterprise_user_account_deletion?`, typically `NoMethodError` on a nil `enterprise_group`. - [Kibana: flag change history](https://log.gprd.gitlab.net/goto/d060337c017723084c6d97e09e591fc6) — confirm each rollout step landed and when. - Kibana: `json.feature_flag_states: "deleting_account_disabled_for_enterprise_users:1"` — confirm the flag resolves for the targeted group. - [feature-flag-log](https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/-/issues) — auto-created audit trail per production change. - Manual check after each step, since over-blocking is metrically silent: enterprise user in an opted-in group is blocked, enterprise user in a default group is not, non-enterprise user is unaffected. ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete deleting_account_disabled_for_enterprise_users --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set deleting_account_disabled_for_enterprise_users false # production /chatops gitlab run feature set deleting_account_disabled_for_enterprise_users false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete deleting_account_disabled_for_enterprise_users --dev --pre --staging --staging-ref --production # remove entirely ```