forked from kata-containers/kata-containers
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tools: Allow setting policy rego file via environment variable #123
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
danmihai1
approved these changes
Dec 13, 2023
12 tasks
sprt
added a commit
that referenced
this pull request
Dec 19, 2023
all-allowed.rego now lives under src/kata-opa/ and set-policy-allowed.rego will be reintroduced by #123 in the same location.
sprt
added a commit
that referenced
this pull request
Dec 19, 2023
all-allowed.rego now lives under src/kata-opa/ and set-policy-allowed.rego will be reintroduced by #123 in the same location.
43200cf
to
1a5105d
Compare
sprt
added a commit
that referenced
this pull request
Dec 20, 2023
all-allowed.rego now lives under src/kata-opa/ and set-policy-allowed.rego will be reintroduced by #123 in the same location.
sprt
pushed a commit
that referenced
this pull request
Dec 20, 2023
* Set policy file via env var * Add restrictive policy file to kata-opa folder * Change restrictive policy file name * Change relative default path location
Redent0r
pushed a commit
that referenced
this pull request
Jun 25, 2024
environment variable (#123) * Set policy file via env var * Add restrictive policy file to kata-opa folder * Change restrictive policy file name * Change relative default path location
Redent0r
pushed a commit
that referenced
this pull request
Jun 27, 2024
environment variable (#123) * Set policy file via env var * Add restrictive policy file to kata-opa folder * Change restrictive policy file name * Change relative default path location * Add license headers
Redent0r
pushed a commit
that referenced
this pull request
Jun 27, 2024
environment variable (#123) * Set policy file via env var * Add restrictive policy file to kata-opa folder * Change restrictive policy file name * Change relative default path location * Add license headers Signed-off-by: Saul Paredes <[email protected]>
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.
This change introduces a new variable to rootfs.sh that allows setting a different rego policy file for the UVM.
The current behavior is unchanged as allow-all.rego is still set by default.
This change also introduces a new file, set-policy-allowed.rego alongside allow-all.rego to enable setting a restrictive initial policy file, requiring all pod YAMLs to carry proper policy annotations.