Don't include compliance pipeline definition in scheduled security orchestration pipelines
requested to merge 352969-security-policy-definition-not-respected-with-scheduled-scan-action into master
What does this MR do and why?
Currently, scan execution policies with type: schedule do not execute their scans if the project has an associated compliance pipeline configuration. Instead, only the compliance pipeline configuration is included.
See: #352969 (closed)
Screenshots or screen recordings
n/a
How to set up and validate locally
See How to reproduce.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #352969 (closed)
Edited by Dominic Bauer