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
Description
Imho, cosign tends to produce confusing output to stdout and stderr. There seems occur a mixture of both in some cases. When failing, the output often appears "unhandled" such as the following:
Error: no matching signatures:
signature not found in transparency log
main.go:62: error during command execution: no matching signatures:
signature not found in transparency log
This is not only hard to interpret as a human, it moreover complicates integration with other tools because the output needs to be parsed and interpreted and as it has not been strictly defined in the past it change throughout the versions.
How to resolve?
Besides returning proper error messages for readability, defining exit codes would simplify integration with other tools. At Connaisseur, we have been struggling to parse the "unhandled" errors.
The text was updated successfully, but these errors were encountered:
Description
Imho, cosign tends to produce confusing output to stdout and stderr. There seems occur a mixture of both in some cases. When failing, the output often appears "unhandled" such as the following:
This is not only hard to interpret as a human, it moreover complicates integration with other tools because the output needs to be parsed and interpreted and as it has not been strictly defined in the past it change throughout the versions.
How to resolve?
Besides returning proper error messages for readability, defining exit codes would simplify integration with other tools. At Connaisseur, we have been struggling to parse the "unhandled" errors.
The text was updated successfully, but these errors were encountered: