You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, grype prints all results in table format to stdout. In the pipeline I want to show the vulnerabilities in human-readable table format and also exporting the scan results into a file but audit/provenance purposes.
$ grype oci-dir:output --fail-on critical -o json --file result.json
Report written to "result.json"
1 error occurred:
* discovered vulnerabilities at or above the severity threshold
Current workaround is to run grype twice with different flags (which decreases UX and increases pipeline duration):
@Dentrax I think we could update the commands surface area to give you the ability to both print the results and write to some destination. @wagoodman would you want this to be added as an additional flag?
Thanks for the issue @Dentrax! I'm going to close this as a duplicate of #648, as it was opened first and has a little more detail -- but please let me know if I've missed something!
By default, grype prints all results in table format to stdout. In the pipeline I want to show the vulnerabilities in human-readable table format and also exporting the scan results into a file but audit/provenance purposes.
Current workaround is to run grype twice with different flags (which decreases UX and increases pipeline duration):
I could
$ cat result.json
here to show content of file, but it's too verbose and does not make sense to print the entire file into stdout.Any thoughts how to achieve this?
cc @developer-guy
The text was updated successfully, but these errors were encountered: