Add tool to generate rumble json files for detected vulnerabilities #890
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
Signed-off-by: Jamon Camisso <jamonation+git@gmail.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
jamonation
changed the title
|
With a little finessing of IAM ServiceAccount settings courtesy @jspeed-meyers, got this action working! https://github.com/chainguard-dev/edu/actions/runs/5836886137/job/15831360816 So I think it is ready to merge and iterate on e.g. adding tests since it needs them badly. |
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.
Type of change
platform
What should this PR do?
This adds a github workflow to generate JSON files for each vulnerability that Rumble detects in external images and Chainguard Images.
What are the acceptance criteria?
The Github action for this should run, and files should be publicly accessible in the GCS bucket.
How should this PR be tested?
Run the action