## Summary Roll out the feature currently behind the `duo_cli_enabled_setting` feature flag. - DRI: @mltheuser.gitlab - Team Slack channel: `#g_editor_extensions` > [!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 blast radius: the flag only gates exposure of the `duo_cli_enabled` admin application setting (which itself defaults to `true`). No data writes, migrations, or shared state. Worst case is the setting becoming visible/usable before intended. Watch `web` and `api` Apdex on https://dashboards.gitlab.net. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_editor_extensions`. 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 duo_cli_enabled_setting 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set duo_cli_enabled_setting true --dev --pre --staging --staging-ref **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): /chatops gitlab run feature set duo_cli_enabled_setting --actors Or target specific actors instead: /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss duo_cli_enabled_setting true /chatops gitlab run feature set --group=gitlab-org,gitlab-com duo_cli_enabled_setting true /chatops gitlab run feature set --user=mltheuser.gitlab duo_cli_enabled_setting 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 — gitlab-lsp reads `requires_duo_cli_enabled` ## 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 /chatops gitlab run feature delete duo_cli_enabled_setting --dev --pre --staging --staging-ref --production ## Rollback /chatops gitlab run feature set duo_cli_enabled_setting false # production /chatops gitlab run feature set duo_cli_enabled_setting false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete duo_cli_enabled_setting --dev --pre --staging --staging-ref --production # remove entirely