fix: Use system field in OPA policies#1048
Open
MohidSheraz wants to merge 1 commit into
Open
Conversation
Signed-off-by: Mohid Sheraz <msheraz@andrew.cmu.edu>
Collaborator
|
as expected - there is a merge conflict now |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update system-scoped reader policies to useinput.credentials.system, matching the field serialized by the RustCredentials type.
Update the corresponding Rego test inputs to use the same system field.
This restores policy rules that were previously checking the nonexistentcredentials.system_scope field.
Closes #1045.
Testing
Ran OPA formatting validation with OPA 1.16.2 in Docker
Ran OPA policy tests with OPA 1.16.2 in Docker
Ran git diff --check
Note: was made with assistance of CodeX.