mirror of
https://github.com/anchore/grype
synced 2024-11-10 06:34:13 +00:00
afc9de6058
* use named pipe bit on stdin as indicator for piped input Signed-off-by: Alex Goodman <alex.goodman@anchore.com> * ensure stdin is ignored when the CLI hints are present Signed-off-by: Alex Goodman <alex.goodman@anchore.com> * add CLI test to cover subprocess integration behavior Signed-off-by: Alex Goodman <alex.goodman@anchore.com> * added test case for java regression Signed-off-by: Alex Goodman <alex.goodman@anchore.com> * remove extra line in makefile Signed-off-by: Alex Goodman <alex.goodman@anchore.com>
20 lines
814 B
Go
20 lines
814 B
Go
package internal
|
|
|
|
import (
|
|
"fmt"
|
|
"os"
|
|
)
|
|
|
|
// IsPipedInput returns true if there is no input device, which means the user **may** be providing input via a pipe.
|
|
func IsPipedInput() (bool, error) {
|
|
fi, err := os.Stdin.Stat()
|
|
if err != nil {
|
|
return false, fmt.Errorf("unable to determine if there is piped input: %w", err)
|
|
}
|
|
|
|
// note: we should NOT use the absence of a character device here as the hint that there may be input expected
|
|
// on stdin, as running grype as a subprocess you would expect no character device to be present but input can
|
|
// be from either stdin or indicated by the CLI. Checking if stdin is a pipe is the most direct way to determine
|
|
// if there *may* be bytes that will show up on stdin that should be used for the analysis source.
|
|
return fi.Mode()&os.ModeNamedPipe != 0, nil
|
|
}
|