Add cascading settings for duo custom agents and flows
What does this MR do and why?
This MR adds database migrations to control Custom Agents and flows at the namespace or instance level, following the cascading settings pattern https://docs.gitlab.com/development/cascading_settings/.
Changes:
- Adds database migration for cascading settings columns. These columns are
default: true, so in next MRs when we use this settings, this will not make any impact on existing behaviour. - Configures columns as cascade attributes at the model level
- Sets up controller-level allowance for these attributes
This MR focuses on the foundational setup only. The settings are not yet integrated into the codebase or exposed in the UI - those will be addressed in follow-up MRs.
This breaks down a larger MR into smaller, reviewable chunks to improve iteration and reduce review complexity (see #594615 (comment 3265765653)).
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
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 #594615 (closed)
Edited by Jaydip Pansuriya