It would be really helpful to be able to use this wrapper in my CI process without needing to include a particular binary in the image. So, it would be great if it were possible to specify a binary or docker backend when instantiating the wrapper.
I am proposing introducing both a GrypeBinaryBackend and a GrypeDockerBackend, an instance of which which can be optionally passed to the Grype constructor. All grype executable calls would be proxied through the specified backend instance. In the event a backend instance is not provided to the constructor, the default is to use a local binary named "grype" as per current usage.
It would be really helpful to be able to use this wrapper in my CI process without needing to include a particular binary in the image. So, it would be great if it were possible to specify a binary or docker backend when instantiating the wrapper.
I am proposing introducing both a
GrypeBinaryBackend
and aGrypeDockerBackend
, an instance of which which can be optionally passed to theGrype
constructor. All grype executable calls would be proxied through the specified backend instance. In the event a backend instance is not provided to the constructor, the default is to use a local binary named "grype" as per current usage.