You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Open Policy Agent is soon to be releasing v1 - the major implication for the Lula project is where users create Lula Validations utilizing the opa-provider the syntax of the rego will change, specifically as described by this reference.
Describe the solution you'd like
Given validation uses the opa-spec with either v1 or v0 rego
When validation is executed
Then it works
Additional context
The OPA provider appears to provide a v0-compatible setting, so we can use the same library to interpret both v1 and v0 rego.
A possible plan may be to update the opa-spec such that a version is requested (v0 or v1). Default could be v0 until a specified date where we switch to v1 as the default? Is there an eventual deprecation of v0?
Expected Deliverable
Discussion + Plan to address (create any associated follow-on issues)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Open Policy Agent is soon to be releasing v1 - the major implication for the Lula project is where users create
Lula Validations
utilizing theopa-provider
the syntax of the rego will change, specifically as described by this reference.Describe the solution you'd like
Additional context
The OPA provider appears to provide a v0-compatible setting, so we can use the same library to interpret both v1 and v0 rego.
A possible plan may be to update the opa-spec such that a version is requested (
v0
orv1
). Default could be v0 until a specified date where we switch to v1 as the default? Is there an eventual deprecation of v0?Expected Deliverable
Discussion + Plan to address (create any associated follow-on issues)
The text was updated successfully, but these errors were encountered: