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
Please provide a set of steps on how to reproduce the issue
grype-db build --provider-name alpine
[0000] INFO grype-db version: 0.19.1
[0000] INFO building database build-directory=./build providers=[] schema=5
[0000] INFO database created path=build/vulnerability.db
What happened:
Passing any --provider-name flags seems to result in no providers being selected and therefore results in an empty database being built.
What you expected to happen:
grype-db build --provider-name alpine
[0000] INFO grype-db version: 0.19.1
[0000] INFO building database build-directory=./build providers=[alpine] schema=5
[0000] INFO database created path=build/vulnerability.db
Anything else we need to know?:
I could have sworn I've used this before, but it seems not to work correctly in any release I've tried so far
westonsteimel
changed the title
Filtering providers using the --provider-name option seems to no longer work
Filtering providers using the --provider-name option seems to result in no providers being selected
Sep 27, 2023
Ah, I forgot to add -g, so it wasn't generating a vunnel config
grype-db build --provider-name alpine -g works as expected
grype-db --provider-name github build -g
[0000] INFO grype-db version: 0.19.1
[0001] INFO building database build-directory=./build providers=[github] schema=5
[0005] INFO database created path=build/vulnerability.db
Please provide a set of steps on how to reproduce the issue
What happened:
Passing any
--provider-name
flags seems to result in no providers being selected and therefore results in an empty database being built.What you expected to happen:
Anything else we need to know?:
I could have sworn I've used this before, but it seems not to work correctly in any release I've tried so far
Environment:
grype-db version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: