-
Notifications
You must be signed in to change notification settings - Fork 574
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
Add db search subcommand #2031
Add db search subcommand #2031
Conversation
Signed-off-by: Tomer Seinfeld <[email protected]>
Signed-off-by: Tomer Seinfeld <[email protected]>
Signed-off-by: Tomer Seinfeld <[email protected]>
Signed-off-by: Tomer Seinfeld <[email protected]>
Signed-off-by: Tomer Seinfeld <[email protected]>
👋 We will discuss this topic at our next Open Source Gardening Live Stream later today. Anyone interested in the topic is welcome to join. All the details are in this thread 🎉 |
If you pull down this branch the easiest way to get this running is the following example:
Is query the correct word? Query to me is usually associated with What do people think about just basic |
Signed-off-by: tomersein <[email protected]>
I've changed the terminology, removed the id flag. returns:
|
Signed-off-by: tomersein <[email protected]>
Signed-off-by: tomersein <[email protected]>
Signed-off-by: tomersein <[email protected]>
Signed-off-by: tomersein <[email protected]>
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.
Sorry for the back-and-forth, I think this is really the last details
Signed-off-by: tomersein <[email protected]>
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.
Thanks for this @tomersein
@tomersein it looks like you might just need to make a couple fixes here for the static analysis thing, and there seems to be an issue with a failing test -- shout if you want me to push any changes for it |
Signed-off-by: tomersein <[email protected]>
Signed-off-by: tomersein <[email protected]>
fixed the lint & the UT @kzantow |
Signed-off-by: tomersein <[email protected]>
Signed-off-by: Keith Zantow <[email protected]>
Thanks for the contribution, @tomersein (and sorry for the back-and-forth) |
Sometimes I want to understand if the DB has the vulnerability I am looking for.
Today in order to do that I need to go to listing.json -> get the latest URL -> Download it -> open DBeaver -> use a simple SQL query.
This PR creates a new endpoint which can accomplish it in a simple command grype explore cve <cve_id>
Fixes #1629