simar7

Currently Trivy follows the [UNIX philosophy of exit codes](https://tldp.org/LDP/abs/html/exitcodes.html). A non zero exit code implies something "undesirable" happened. The exit code is supposed to be set by the user, therefore...

All yours @krol3 👍

hi @rcarpio-hbo - thanks for the idea but what is the use case for such a feature? The current Trivy GitHub Action is meant for CI pipelines to be automatically...

hi @javixeneize - you could set a conditional of ` - if: always()` with your Upload artifact step. Something like this: ``` - name: Run Trivy vulnerability scanner uses: aquasecurity/trivy-action@master...

Do you mean if a Trivy scan would expose this information?

As discussed offline before (and Daniel's link above), this is something we need to engage the GitHub team to do for us as they don't provide a self serve option.

thanks @larryclaman for reporting this - we'll take a look @krol3 could you check if your unit tests are able to reproduce this issue locally?

> @kgeorgiou Thanks for pointing this out. Couple of thoughts: > > 1. Why is this not documented? (eg why is this 'design choice' only buried in the code?) Note:...

hi @delprofundo - would you have more info on how you ran trivy action in this case? we currently use the error code to signal the CI pipeline to pass/fail...

> Not sure if this is an edge case, but I have the need for scanning multiple, dynamically-named images in a single job and failing the action if any of...