Closed DmitriyLewen closed 2 weeks ago
I used Alias
.
But I thought the report.go file would be better suited for this flag.
So i moved this flag to this file + rename flag + add Alias
.
https://github.com/aquasecurity/trivy/blob/5bc3fa79de38fa03e705c2db269b88acfc262b67/pkg/flag/report_flags.go#L109-L122
I don't think it's a breaking change. People can keep using --vuln-type. We should announce the deprecation. After a while, we'll delete it, then it'll be a breaking change as the same command no longer works.
It is always difficult to determine the type of PR, but I think it will be a "refactor" when there is no user impact. In this case, UI will be changed. It's not a new feature or bug fix, but I think "feat" is the closest.
I don't think it's a breaking change
I thought about this.
I renamed VulnType
to PkgTypes
e.g.:
These are breaking changes for users using Trivy as a library.
It is always difficult to determine the type of PR, but I think it will be a "refactor" when there is no user impact. In this case, UI will be changed. It's not a new feature or bug fix, but I think "feat" is the closest.
hm... okay, i will change type of PR.
These are breaking changes for users using Trivy as a library.
That's a good point. But Trivy is a CLI tool. We could consider whether changing to CLI usage is destructive. Of course, we should ensure the change is minimal for tools importing Trivy, though. Otherwise, adding arguments to an internal function will be a breaking change if it is exported.
@naortalmor1 @tamirkiviti13 @tonaim We changed a variable name. I don't think it will have a major impact, but I thought I'd let you know just in case.
Okay. I got you.
I updated type
of PR
It's not an issue from this PR, but logging doesn't seem to be enabled well. I mean our custom handler is not initialized, and the log format is different.
Created #7124 for this.
Description
Rename
--vuln-type
flag to--pkg-types
flag. See #6269Before:
After:
Related issues
Checklist