## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/633566) currently behind the `slack_duo_group` feature flag. - DRIs: jannik_lehmann, knejad - Team Slack channel: `#f_external_agents` > [!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 the flag does **Off (today's behaviour):** an `@GitLab` mention in Slack starts a GitLab Duo session in the mentioning user's own default Duo namespace. **On (new behaviour):** the session runs and is billed in the one top-level group that an Owner chose for that Slack workspace. A workspace without a chosen group gets a reply explaining who can turn GitLab Duo on, and no session starts. ## What could go wrong? - **Blast radius:** only the `@GitLab` mention path of the GitLab for Slack app. Slack notifications and slash commands do not read the flag and are unaffected. - **Workspaces without a chosen group stop working** while the flag is on for them. That is the intended end state, but it means every workspace we enable needs an Owner to pick a group first. **Our own workspaces must be claimed before the first rollout step**, otherwise we break our own dogfooding. - **Billing moves.** Sessions start consuming credits in the chosen group instead of each user's own namespace. Nothing is charged twice, but the group that pays changes. - **Actor:** the group. Enable per top-level group first, never per user: a Slack workspace is shared by many users, so a per-user rollout would make the same workspace behave differently per person. ## Rollout order 1. Claim the Duo group for our own Slack workspaces that use GitLab Duo. 2. `--group=gitlab-org,gitlab-com` and dogfood for two to three days. 3. Known beta groups, after telling them in the beta channel. 4. 100% soon after the beta groups. Skip a slow percentage rollout: while the flag is on for some groups only, users can get `flow_not_enabled` (see !266172). 5. `default_enabled: true` for Self-Managed in 19.7, in the same milestone as `slack_duo_api_flow` (#628672). Shipping only one of the two makes Self-Managed mentions fail with `flow_not_enabled`. ## Events <!-- Replace feature flag name in the link--> - [Exceptions with slack_duo_group:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.exception.feature_flag_states.keyword:%22slack_duo_group:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with slack_duo_group:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.feature_flag_states:%22slack_duo_group:1%22'),columns:!(json.meta.caller_id,json.feature_flag_states),sort:!(!(json.time,desc)))) - [Error rate and other graphs by modifying the examples in the Visualization Library](https://log.gprd.gitlab.net/app/visualize#/?_g=h@358d019&s=FF%20Observability) Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#f_external_agents`. 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 slack_duo_group 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set slack_duo_group true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set slack_duo_group <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss slack_duo_group true /chatops gitlab run feature set --group=gitlab-org,gitlab-com slack_duo_group true /chatops gitlab run feature set --user=<gitlab-username-of-dri> slack_duo_group true ``` ## 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/-/work_items/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 slack_duo_group --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set slack_duo_group false # production /chatops gitlab run feature set slack_duo_group false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete slack_duo_group --dev --pre --staging --staging-ref --production # remove entirely ```