Upgrade to opa v1.0.1 #3407
Open
Upgrade to opa v1.0.1 #3407
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
Pushpalanka
force-pushed
the
upgrade-opa-v1.0.1
branch
from
26e2bad to
987c73e
Compare
Pushpalanka
added
dependencies
Pushpalanka
force-pushed
the
upgrade-opa-v1.0.1
branch
2 times, most recently
from
8409a1e to
1600aed
Compare
Signed-off-by: Pushpalanka Jayawardhana <[email protected]>
Pushpalanka
force-pushed
the
upgrade-opa-v1.0.1
branch
from
1600aed to
dba5d43
Compare
|
LGTM |
|
Let's just align internally before merging this to validate all existing policies are ready. |
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.
Note: This OPA version upgrade can possibly break current Skipper OPA filter usages, if the policies are not using rego.v1 syntax.
The changes contains below,
Upgrading from OPA 0.70.0 to 1.0.1