Enable scans for vulnerabilities #18
Labels
enhancement
New feature or request
Comments
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6296.
|
DnPlas
changed the title
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6342.
|
DnPlas
added a commit
that referenced
this issue
Oct 16, 2024
…ssues This workflow enables a scheduled scanner (that can also be run from a workflow dispatch) to scan images using the trivy scanner. At the same time, enables the automatic creation/edition of Github issues when a vulnerability is found. Fixes #18
DnPlas
added a commit
that referenced
this issue
Oct 17, 2024
…ssues (#19) * ci: enable scheduled trivy scanner and report vulnerabilities as GH issues This workflow enables a scheduled scanner (that can also be run from a workflow dispatch) to scan images using the trivy scanner. At the same time, enables the automatic creation/edition of Github issues when a vulnerability is found. Fixes #18
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
The mlflow rock is not currently scanned for vulnerabilities, but it must be ensured it is as part of the team's vulnerability response. This effort means enabling vulnerability scans and automated reports for the rock.
What needs to get done
Ensure the rock repository is using the reusable workflow for oci-images proposed in canonical/charmed-kubeflow-workflows#69 for:
Definition of Done
The reusable workflow is in place and runs on merge, schedule runs, and a workflow dispatch is enabled.
The text was updated successfully, but these errors were encountered: