-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
enhancement(python): use one info and multiple debug logs for License acquired from METADATA...
message
#8160
Comments
Thanks for promoting this to an issue. Out of interest why is it necessary to be running this license code at all when |
this is a feature of the cache |
I see, maybe there shouldn't be even 1 line at INFO level unless you have the |
There is a problem with this. |
Hum, perhaps at this stage it shouldn't log anything then (this doesn't seem like an error) and if there is something important to flag to the user then the |
There are challenges with this as well because the METADATA file has 4 fields for licenses, and Trivy parses these fields in the parser and only passes the resulting values to the cache. It will be quite problematic to determine which specific field the license was obtained from after retrieving the cache. |
Interesting ok, I'm unfamiliar with the details behind Even seeing that one line I wouldn't really be sure what to do about it but that's a separate question! |
The license scanner is to detect license problems. Trivy shows package information, such as package name, version, license, etc., regardless of whether the license scanning is enabled. |
Description
License acquired from METADATA classifiers may be subject to additional terms
messages can be too noisy.So we need to use
Once
to show a singleInfo
log and move these messages to theDebug
level.See #8159 for example.
Discussed in #8159
The text was updated successfully, but these errors were encountered: