Resolve Runtime variable during OPA evaluation.
long-term
C
Cooing Rook
I don't see any reason that the OPA policy engine couldn't
try
to resolve variables for Pipeline Run Policy Sets before evaluation or even add them to the JSON output to avoid breaking backward compatibility so you can enable your customers to do both pre-resolution and post-resolution validation via OPA/Rego. I realize it won't be able to resolve many of those variables such as step or stage output variables, but for Runtime Inputs and Pipeline/Project/Org/Account Variables it would let me add meaningful governance without forcing complex pipelines on our teamsC
Comfortable Gayal
Can we get a status update on this one? It's been a bit over 2 months since we last heard what is happening with this and this feature is very useful for us.
J
Jade Aardvark
Rohan Gupta I wanted to check in on the progress of this implementation?
Rohan Gupta
updated the status to
long-term
Reviewed with customer on call today to clarify use case, we do plan on addressing this capability. Currently building out the PRD.
Rohan Gupta
updated the status to
rejected
We are not planning on supporting Harness Expressions and Variables in OPA Policies. You can use the OPA Policy Step to Map Pipeline Variables outputs to the a input parameter in the policy. Thats the purpose of it.