Release AI Catalog as Generally Available

Luke Duncalferequested to merge
570161-ga-with-ai_duo_agent_platform_ga_rollout into master

What does this MR do and why?

This MR updates the AI Catalog's GA status to observe the ai_duo_agent_platform_ga_rollout flag as introduced in !213425 (merged).

This releases the AI Catalog as Generally Available:

  • For SaaS, when on ai_duo_agent_platform_ga_rollout feature flag is enabled.
  • For SM, always!

This makes the AI Catalog available for a group/project:

  • On SM: Always
  • On Saas: If the ai_duo_agent_platform_ga_rollout is disabled, only when they have opted into Experimental/Beta AI features (current state on GitLab.com). When ai_duo_agent_platform_ga_rollout is enabled

Note that flows are not being released in this MR. The ai_catalog_flows flag is being set to enabled in !214872 (merged) rather than this MR, as we will only enable flows globally when that feature is redefined as Beta.

Note the frontend badges are being updated to observe the ai_duo_agent_platform_ga_rollout in !215064 (merged).

References

How to set up and validate locally

Delete your previously enabled flag states for the AI Catalog features:

Feature.remove(:global_ai_catalog)
Feature.remove(:ai_agents)
Feature.remove(:ai_third_party_flows)
Feature.reset

Running your instance as SaaS, and with a top-level group that has enabled AI Experimental/Beta features, you should be able to use the AI Catalog features as normal:

  • Visit http://gdk.test:3000/explore/ai-catalog
  • You should be able to create agents/flows for the project, and enable them
  • The Automate menu should be displaying for the project
  • You should be able to use agentic chat with custom agents, enable external agents/third party flows, and execute them

Now, switch the top-level group to disable AI Experimental/Beta features:

  • For project's top-level group, go Settings > GitLab Duo:
    • Click Change configuration
    • Ensure GitLab Duo is On by default
    • Ensure Turn on experiment and beta GitLab Duo features is not selected

As a SaaS instance, if this was the only top-level group with Duo Enabled that you were a member of, you will now not be able to access the AI Catalog at the explore-level. It will display as a 404.

As a SaaS instance, if there were other groups with Duo Enabled, you will be able to access the catalog but not be able to interact with AI Catalog features with that group/projects in that group.

  • Visit http://gdk.test:3000/explore/ai-catalog
  • You should not be able to create agents/flows for the project, or enable them
  • The Automate menu should not be displaying for the project, and accessing the routes directly should result in a 404

Now run your instance as SM, you should be able to interact with the AI Catalog.

Now run your instance as SaaS again, but this time enable the ai_duo_agent_platform_ga_rollout feature flag, you should be able to interact with the AI Catalog.

If you had enabled ai_catalog_flows, disable or remove the flag now, and notice that Flows feature correctly is not available yet.

Feature.remove(:ai_catalog_flows)

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.

Related to #570161

Edited by Luke Duncalfe

Merge request reports