Remove warn mode feature flags on backend
What does this MR do and why?
Remove warn mode feature flags on backend
- feature flag policy_violations_es_filter
- feature flag security_policy_approval_warn_mode
- update tests
Changelog: removed
EE: true
References
Screenshots or screen recordings
| Page | Screenshot |
|---|---|
| Policy Editor |
|
| Policy list |
|
| MR approval |
|
| MR Bot comment |
|
| MR bypassed |
|
| Vulnerability List |
|
How to set up and validate locally
- Upload a GitLab Ultimate license
- Navigate to a project => Secure => Policies => New policy => Merge request approval widget
- Verify the policy has the enablement section and it defaults to
Warn - Verify the only action that can be added is
Warn in merge request - Create a warn mode policy that is required on when there are vulnerabilities
- Navigate to a project => Secure => Policies => Select the new policy => Verify the drawer says it is a warn mode policy
- Create a merge request in the project with vulnerabilities
- Verify the MR is blocked by the policy because the pipeline finds the vulnerabilities
- Verify the user can override the policy
- Merge the MR
- Navigate to the project => Secure => Vulnerability report
- Verify the vulnerabilities show up in the report with a new badge
- Verify a user can filter by these vulnerabilities
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 #580658 (closed)
Related to #577591 (closed)
Edited by Alexander Turinske





