Foundational agents: per-agent settings

What does this MR do and why?

Adds per-agent configuration to admin and group GitLab Duo settings. The foundational agents radio button now sets the default availability, which can be overridden per agent using a dropdown. The availability options include:

• Enabled
• Disabled
• Use default: based on the foundational agents default availability

These changes are hidden behind a WIP feature flag duo_foundational_agents_per_agent_availability as the BE changes are currently in flight.

References

• [Foundational agents] Enabling individual agent... (#579738 - closed)

Screenshots or screen recordings

Admin	Group
admin	group

How to set up and validate locally

Prerequisites:

• As the BE MRs for per-foundational agents configuration is currently in flight, refer to the following branches to test out the FE changes: ch-579738-test
• Pull branch and run migrations: bin/rails db:migrate
• Enable duo_foundational_agents_per_agent_availability feature flag

Admin:

• Run GDK on non-SAAS mode: GITLAB_SIMULATE_SAAS=0 gdk start
• Go to admin Duo settings page: /admin/gitlab_duo/configuration

Group:

• Run GDK on SAAS mode: GITLAB_SIMULATE_SAAS=1 gdk start
• Go to the group Duo settings page: /groups/gitlab-duo/-/settings/gitlab_duo/configuration

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.