Disable license scanning for warn mode
What does this MR do and why?
Disable license scanning for warn mode
- license scanning will not be enabled for warn mode initially due to technical constraints
- remove it from the dropdown when warn mode is selected
- update the banner to mention this
- disable warn mode selection if license scanning is already selected
EE: true
References
Screenshots or screen recordings
| Scenario | Screenshot |
|---|---|
| Warn mode selected - remove license scanning from dropdown | ![]() |
| License scanning selected - disable warn mode | ![]() |
| Disabled rule mode if incorrect syntax created in yaml mode | ![]() |
How to set up and validate locally
- Upload a GitLab Ultimate license
- Enable the
security_policy_approval_warn_modefeature flag (http://gdk.test:3000/rails/features) - Navigate to a project/group => Secure => Policies => New policy => Merge Request Approval Policy
- Verify in warn mode, license scanning cannot be added
- Verify in enforce mode, if license scanning is added, warn mode is disabled
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 #549783 (closed)
Edited by Alexander Turinske


