<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=599968) </details> <!--IssueSummary end--> <!-- Title: [FF] `duo_developer_orbit` -- Route developer/v1 to orbit flow version --> ## Summary This issue is to roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/599229) on production, that is currently behind the `duo_developer_orbit` feature flag. When enabled for a user, and the user has the Orbit master toggle turned on in their preferences, the `developer/v1` foundational flow is routed to the `2.0.0-orbit` flow version instead of the default `2.0.0`. This allows internal testing of the Orbit-aware developer flow variant without affecting other users. ## Owners - Most appropriate Slack channel to reach out to: `#g_agent_foundations` - Best individual to reach out to: @thomas-schmidt ## Expectations ### What are we expecting to happen? When the feature flag is enabled for a user: - If the user has also turned on the Orbit master toggle in their preferences, triggering Duo Developer will use the `2.0.0-orbit` flow version on AI Gateway - If the user has not opted into Orbit, behavior is unchanged (default `2.0.0` version) - The `duo_developer_orbit` flag takes priority over `duo_developer_next_unstable` when both are active, so users can explicitly opt into the orbit flow even when `duo_developer_next_unstable` is globally enabled ### What can go wrong and how would we detect it? If the `2.0.0-orbit` flow version does not exist or has issues on the AI Gateway side, users with the flag enabled would get errors when triggering Duo Developer. This would be visible in workflow execution failures. Rollback is immediate by disabling the feature flag. Since this is a user-actor flag intended for internal testing, the blast radius is limited to explicitly enabled users. ## Rollout Steps Note: Please make sure to run the chatops commands in the Slack channel that gets impacted by the command. ### Rollout on non-production environments - Verify the MR with the feature flag is merged to `master` and has been deployed to non-production environments with `/chatops gitlab run auto_deploy status <merge-commit-of-your-feature>` - [ ] Enable the feature flag for specific test users with `/chatops gitlab run feature set --user=thomas-schmidt duo_developer_orbit true --dev --pre --staging --staging-ref` - [ ] Verify that the feature works as expected for the enabled user. ### Before production rollout - [ ] Ensure the `2.0.0-orbit` flow version is deployed and functional on AI Gateway. ### Specific rollout on production For visibility, all `/chatops` commands that target production must be executed in the [`#production` Slack channel](https://gitlab.slack.com/archives/C101F3796) and cross-posted (with the command results) to the responsible team's Slack channel. - Ensure that the feature MRs have been deployed to both production and canary with `/chatops gitlab run auto_deploy status <merge-commit-of-your-feature>` - [ ] Enable for specific internal test users: `/chatops gitlab run feature set --user=thomas-schmidt duo_developer_orbit true` - [ ] Verify that the feature works for the specific actors. ### Release the feature This feature flag is intended for internal testing of the Orbit developer flow variant. The decision to roll out more broadly or clean up will depend on evaluation results comparing the orbit and non-orbit developer flows. - [ ] Create a merge request to remove the `duo_developer_orbit` feature flag once a decision is made on the orbit flow integration approach. - [ ] Close [the feature issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/599229) to indicate the feature will be released in the current milestone. - [ ] Once the cleanup MR has been deployed to production, clean up the feature flag from all environments by running these chatops command in `#production` channel: `/chatops gitlab run feature delete duo_developer_orbit --dev --pre --staging --staging-ref --production` - [ ] Close this rollout issue. ## Rollback Steps - [ ] This feature can be disabled on production by running the following Chatops command: ``` /chatops gitlab run feature set duo_developer_orbit false ``` - [ ] Disable the feature flag on non-production environments: ``` /chatops gitlab run feature set duo_developer_orbit false --dev --pre --staging --staging-ref ``` - [ ] Delete feature flag from all environments: ``` /chatops gitlab run feature delete duo_developer_orbit --dev --pre --staging --staging-ref --production ```