-
Notifications
You must be signed in to change notification settings - Fork 28
feat: output results in reusable workflow #100
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
base: main
Are you sure you want to change the base?
Conversation
|
Resolves #99 |
6c45f1f to
e004680
Compare
|
Sorry for the delay! I'm still not very happy with the base64 option, as it would mean the parser would need to know to first run it through a b64decode. Alternatively, I think having a random delimiter and multiline string might be an option? |
I like your approach much better. Let me work on it. Thanks! |
Done! |
another-rex
left a comment
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.
Thanks! Looking good!
Exporting the results of the OSV scan in an output variable of the workflow will allow them to be used in later workflow jobs for example to decide under which conditions the workflow should fail.
Here is a basic example of how the output could be used to fail the workflow if there is any result:
A tool like
jqcould be used to write much more elaborate conditions based on the content of the results (severity, CVSS score, package name etc.).