Ignore config sources by default with overriding PEP
What does this MR do and why?
- Prevent unnecessary processing of AutoDevops with overriding PEP.
- Ignore
ComplianceandParametersources with overriding PEP, making "dry run" / config validation consistent with the pipeline run
When overriding pipeline execution policies are in place, AutoDevops and other configs are loaded, processed, and ignored later in the chain here.
This change skips loading of configs by default when overriding pipeline execution policies are in place.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
- Extracted from !178199 (comment 2307822175)
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.
Related to #475152 (closed)
Edited by Martin Cavoj