Support non default branch in OPA Policy
pending feedback
C
Coral reef Lungfish
Currently, the remote flow works correctly for the default branch. However, we need the OPA policies to work on non-default branches as well.
Log In
a
abhijit.pujare
marked this post as
pending feedback
M
Maroon Mockingbird
This is a feature we need to be able to handle blue-green testing. Having just main/master makes this impossible for OPA promotion.
a
abhijit.pujare
Maroon Mockingbird: We are currently working on the capability to allow you to use the testing terminal to test OPA policies on various branches.
With respect to the actual policy evaluation, it will always happen against the policy in the default branch.
M
Maroon Mockingbird
abhijit.pujare that is not our use case. Our use case is to have a different branch for evaluation. So we can have a certain number of workspaces run against a version of the policy in the integration branch, and a different set against the master branch. That way the OPA can be confirmed as operational against the full suite but a subset of the overall cluster of workspaces. Then a merge to master automatically makes it usable by the other set.
Shylaja Sundararajan
marked this post as
long-term