-
Notifications
You must be signed in to change notification settings - Fork 0
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
ci: add workflow to enable automatic vulnerability reports #72
Merged
DnPlas
merged 7 commits into
KF-6331-dev-branch
from
KF-6331-report-vulns-as-github-issues
Oct 11, 2024
Merged
ci: add workflow to enable automatic vulnerability reports #72
DnPlas
merged 7 commits into
KF-6331-dev-branch
from
KF-6331-report-vulns-as-github-issues
Oct 11, 2024
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
This re-usable workflow can be used for reporting security vulnerabilities via Github issues. It takes the issue title, image-name, and issue-labels as inputs, and in turn: * edits an existing issue with the same title and updates the vulnerability report * creates a new issue with the issue-title and adds the vulnerability report in the description Please NOTE this workflow assumes the existence of vulnerability reports as artefacts of a workflow run; that is, it expects artefacts named trivy-report-<image-name> to be present in the sabe workflow run. Part of #69
orfeas-k
reviewed
Oct 10, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, I like the result. Left some comments
orfeas-k
reviewed
Oct 10, 2024
orfeas-k
reviewed
Oct 11, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replied to comments, I think we need one or two small updates, other than that LGTM
orfeas-k
approved these changes
Oct 11, 2024
This was referenced Oct 15, 2024
DnPlas
added a commit
that referenced
this pull request
Oct 15, 2024
feat: report vulnerabilities as GH issues and scan images from registry This commit adds: * ci: add re-usable workflow for scans from published img and automatic… (ci: add re-usable workflow for scans from published img and automatic… #73) * ci: add workflow to enable automatic vulnerability reports (ci: add workflow to enable automatic vulnerability reports #72) * chore, ci: bump artifact download/upload and checkout actions v3 -> v4 (chore, ci: bump artifact download/upload and checkout actions v3 -> v4 #71)
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 re-usable workflow can be used for reporting security vulnerabilities via Github issues. It takes the issue title, image-name, and issue-labels as inputs, and in turn:
Please NOTE this workflow assumes the existence of vulnerability reports as artefacts of a workflow run; that is, it expects artefacts named trivy-report- to be present in the sabe workflow run.
Part of #69
For reviewers
This workflow has been tested in this fork. The re-usable workflow is capable of generating these type of issues. Please note how they are edited if the
Scan images
workflow is run multiple times.The workflow that generated those can be found here, and the re-usable workflow that is mentioned there is fully implemented in #73.