Move SAST_EXCLUDED_PATHS to top of vuln filter list
What does this MR do?
Reprioritize SAST vulnerability filter variables to prefer SAST_EXCLUDED_PATHS
We should prefer this one as its a global option and future improvements will go towards improving its matching logic. It's a better experience than calling out the individual configurations unless they are required.
This situation will be better alleviated with completion of #13317
Screenshots
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team