Remove duo_sast_fp_detection cascading setting from namespace/application
What does this MR do and why?
- Remove the cascading behaviour for
duo_sast_fp_detection_enabled, keeping it only at the project level in ProjectSetting. - Add
ignore_columnforduo_sast_fp_detection_enabledandlock_duo_sast_fp_detection_enabledinApplicationSettingandNamespaceSettingmodels. - Remove
cascading_attr, delegations, and availability methods from models - Remove from API params, helpers, presenters, and services
- Remove frontend components and settings for admin/group levels
Closes https://gitlab.com/gitlab-org/gitlab/-/issues/588810
References
Screenshots or screen recordings
Group level setting removed
| 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.
Edited by Huzaifa Iftikhar

