Ignore compliance CI config when source is on-demand DAST scan
What does this MR do and why?
Ignore compliance CI config when source is on-demand DAST scan
Related Issues: #437098 (closed) & #440812 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Setup compliance framework for a project
- Setup an on-demand DAST scan for the same project
- Trigger a new on-demand DAST scan, it should only have the DAST job and not the compliance framework jobs.
Related to #437098 (closed)