OPA Policy Dry Run
pending feedback
R
Rubber Scallop
Before enabling an OPA Policy, we want to know how many pipelines will be impacted by the OPA Policy.
- Understand the radius of the OPA Policy - how many projects and pipelines it is impacting
- Identify errors that will occur when enabling an OPA Policy to fix prior to enabling it
Log In
a
abhijit.pujare
pending feedback
a
abhijit.pujare
Would setting the evaluation criteria to warning work for your use case? When adding a policy set, you can set the eval criteria to "warning." You can then see the impact of the policy on the pipeline the next time it is run and see what the warning gives (this is available via looking at the evaluations). Let me know if this is addresses the Dry-Run type behavior you are looking for.
R
Rubber Scallop
Hi abhijit.pujare The issue which we want to address via dry run is apply the policy with most recently executed pipeline in the account so we know how many pipeline will fail if we release the policy. The issue with warning is "we need to wait for pipeline to execute". If the pipeline is not executed during the warn and if it run after we release them as ERROR then the warning wouldn't be sufficient. Please let me know if you have any question.
Prasad Satam
under review