## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/epics/22921) currently behind the `duo_flow_callback_hooks` feature flag. Registering a callback endpoint lets a flow send signed webhook events for start, completion, and failure instead of requiring clients to poll for status. - DRI: @thomas-schmidt - Team Slack channel: `<slack-channel-of-dri-team>` > [!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? - Malformed or malicious payloads reaching third-party callback endpoints - Retry storms against slow or unresponsive external endpoints, backing up delivery workers - Token leakage letting an attacker attach a flow to an existing hook and receive its events - Blast radius is small: the flag is off by default and enabled per top-level group on request ## Rollout The flag is checked against `container.root_ancestor` at every call site, so the only meaningful targets are a **top-level group** (which covers all its projects and subgroups) or **instance-wide**. Targeting a project, subgroup, or user silently enables nothing — do not use `--project=` or `--user=` for this flag. Rollout model for the experimental release: enable per top-level group on request. No percentage rollout is planned. Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `<slack-channel-of-dri-team>`. 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** — enable for a test group: ``` /chatops gitlab run feature set --group=<group-full-path> duo_flow_callback_hooks true --dev --pre --staging --staging-ref ``` **Production** — enable for the requesting top-level group: ``` /chatops gitlab run feature set --group=<group-full-path> duo_flow_callback_hooks true ``` While the flag is selectively enabled, label this issue `~"feature flag state::rolling out"` so automation reads the state correctly. Note: once [!253993](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/253993) merges, the namespace must also have Duo Agent Platform enabled (`duo_agent_platform_enabled`); the flag alone grants nothing. ## Before global rollout Not needed for the experimental phase above. Confirm the relevant gotchas before any instance-wide or GitLab.com-wide enablement (the beta/GA track in [epic 22923](https://gitlab.com/groups/gitlab-org/-/epics/22923)) — 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 - Confirm attaching a flow to a hook is safe to open beyond org-owner-controlled secrets before any org-wide or GitLab.com-wide rollout (see [merge request discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/247573)) ## 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 duo_flow_callback_hooks --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set --group=<group-full-path> duo_flow_callback_hooks false # one group /chatops gitlab run feature set duo_flow_callback_hooks false # production, globally /chatops gitlab run feature set duo_flow_callback_hooks false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete duo_flow_callback_hooks --dev --pre --staging --staging-ref --production # remove entirely ```