Duo Agent platform sessions support multiple namespaces
What does this MR do and why?
Duo Agent platform sessions support multiple namespaces
In the near future, we will want to support adding the Automate menu under different namespace. Currently some of the data fetching was harcoded to project, so when we need to support group, users, admin, etc we will want it to be easily extensible.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
- Make sure you have AI features enabled https://docs.gitlab.com/development/ai_features/
- Turn on two feature flags:
duo_workflowandduo_workflow_in_ci - Navigate to a project with AI features
- On the left, you will see the Agents menu
- Click on it, it will take you to fullpath/-/automate
- This will load your workflows in that project
- If you have none, notice the empty screen
- If you need to populate flows, run the rake task for your project (ee/lib/tasks/gitlab/duo_workflow/duo_workflow.rake)
bundle exec rake "gitlab:duo_workflow:populate[50,20,user@example.com,gitlab-org/gitlab-test]"- The user here should be the logged in user for you to see them, and the project the one you will test in.
- Navigate to the Automate => Agent sessions page
- Click around all should work
- Check the dev console, no errors!
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Frédéric Caplette