-
Notifications
You must be signed in to change notification settings - Fork 9
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
Use CVEorg keywords from ps-constants #850
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requesting changes to follow the PS Constants collector logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I totally agree with @JakubFrejlach. This is not the way PS constants should be used. There are existing examples which can serve as an inspiration
6730a2f
to
11d320a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for reworking that logic to comply with the ps-constants. I have couple of other objections.
11d320a
to
bfe4dd3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now! Thanks for addressing everything. Good job.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
bfe4dd3
to
375e86c
Compare
This PR changes the CVEorg collector to use keywords from the
ps-constants
repository instead of the ones hardcoded in theosidb
repository. Also, it renamesblacklist
andwhitelist
toblocklist
andallowlist
.Closes OSIDB-3694