Upgrade to OPA v1 #5769
Open
Upgrade to OPA v1 #5769
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
sorindumitru
requested review from
evan2645,
amartinezfayo,
azdagron,
MarcosDY and
rturner3
as code owners
sorindumitru
force-pushed
the
opa-upgrade
branch
from
9b48272 to
30a5222
Compare
Signed-off-by: Sorin Dumitru <sdumitru@bloomberg.net>
sorindumitru
force-pushed
the
opa-upgrade
branch
from
30a5222 to
1f5882f
Compare
Signed-off-by: Sorin Dumitru <sdumitru@bloomberg.net>
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.
The new version is backwards incompatible with the v0 version. This includes the policy language itself, which has become stricter.
The 1.0 API allows specifying the version of the policy at the time of the loading the policy so I'll look into making that configurable to make it easier for users to upgrade. To be decided if we want to default to V1 or V0. Since this is an experimental config, I think we can default to V1.
Pull Request check list
Affected functionality
Description of change
Which issue this PR fixes
closes #5754