feat: added the ability to pass json content not only as a file with the json extension #422
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
…on extension Signed-off-by: Makarii Balashov <[email protected]>
ya-makariy
force-pushed
the
feat/pass-json-without-file-extension
branch
from
60d3381
to
40df200
Compare
ya-makariy
changed the title
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.
Explanation
Added the ability to pass json content not only as a file with the json extension.
Usage Example:
kyverno-json scan --policy catalog/dockerfile/dockerfile-deny-latest-image.yaml --payload <(dockerfile-json /path/to/Dockerfile)Related issue
Milestone of this PR
What type of PR is this
Proposed Changes
Proof Manifests
Checklist
Further Comments