Bump OPA to v0.60.0 #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 7485948483
💛 - Coveralls |
carabasdaniel
force-pushed
the
bumpOPA
branch
from
9ac9f1c
to
917a5bf
Compare
carabasdaniel
force-pushed
the
bumpOPA
branch
from
917a5bf
to
03c2478
Compare
ronenh
approved these changes
Feb 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumping in prep for OPA 1.0 is blocked by: open-policy-agent/opa#6450
Using the runtime in policy CLI to build the OPA policy image should not cause the issue mentioned above.
Having the
--rego-v1flag added to more commands would be nice to allow the runtime build to return the correct errors when a policy is not v1 compatible: open-policy-agent/opa#6463