## Summary Roll out [the `created` merge request Duo Agent Platform flow trigger](https://gitlab.com/gitlab-org/gitlab/-/work_items/592452) currently behind the `merge_request_create_flow_trigger` feature flag. - DRI: @marc_shaw - Team Slack channel: `#g_dap_events` > [!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? Blast radius is every merge request creation on a project that has a `merge_request` flow trigger configured. No data-loss risk: the flag gates whether `MergeRequests::PreparedCloudEvent` is published at all, so with it off nothing is published, no worker is scheduled, and no Redis keys are written. The flag exists primarily to satisfy [Sidekiq compatibility across updates](https://docs.gitlab.com/development/sidekiq/compatibility_across_updates/#adding-new-workers): `Ai::Catalog::Flows::ExecuteMergeRequestPreparedWorkflowTriggersWorker` is a brand new worker schedulable from an HTTP request, and GitLab.com has no Sidekiq canary stage, so without the flag it could be enqueued from canary hours before the Sidekiq fleet can run it. Introduced by https://gitlab.com/gitlab-org/gitlab/-/merge_requests/242698. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_dap_events`. 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 merge_request_create_flow_trigger 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set merge_request_create_flow_trigger true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set merge_request_create_flow_trigger <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss merge_request_create_flow_trigger true /chatops gitlab run feature set --group=gitlab-org,gitlab-com merge_request_create_flow_trigger true /chatops gitlab run feature set --user=marc_shaw merge_request_create_flow_trigger 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/-/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 merge_request_create_flow_trigger --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set merge_request_create_flow_trigger false # production /chatops gitlab run feature set merge_request_create_flow_trigger false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete merge_request_create_flow_trigger --dev --pre --staging --staging-ref --production # remove entirely ``` <!-- Uncomment the appropriate type label /label ~"type::feature" ~"feature::addition" /label ~"type::maintenance" /label ~"type::bug" -->