Describe the bug
When deploying exemptions, if a scope is not found a warning is thrown rather than an error. This means a deploy pipeline will not fail so the end user has no visibility of the failure to deploy the exemption without reviewing the logs in detail.
To Reproduce
Steps to reproduce the behavior:
Perform a deployment with an exemption which has a typo/mis-spelled scope.
(note - "skipResourceValidationForExemptions" is set to 'true' in global settings for the environment due to amount of exemptions in environment to speed up build time)
Expected behavior
A clear and concise description of what you expected to happen.
I would expect that, if a resource (in this case an exemption) that was intended to be deployed and failed, the pipeline result would reflect the failure.
Screenshots
Warning comes from the "Set-AzPolicyExemptionsRestMethod" function, line 42.
Describe the bug When deploying exemptions, if a scope is not found a warning is thrown rather than an error. This means a deploy pipeline will not fail so the end user has no visibility of the failure to deploy the exemption without reviewing the logs in detail.
To Reproduce Steps to reproduce the behavior:
Perform a deployment with an exemption which has a typo/mis-spelled scope.
(note - "skipResourceValidationForExemptions" is set to 'true' in global settings for the environment due to amount of exemptions in environment to speed up build time)
Expected behavior A clear and concise description of what you expected to happen.
I would expect that, if a resource (in this case an exemption) that was intended to be deployed and failed, the pipeline result would reflect the failure.
Screenshots
Warning comes from the "Set-AzPolicyExemptionsRestMethod" function, line 42.
EPAC Version 10.3.1