Container scan eligibility and config validations #957
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds 2 validations to determine if container scan should skip or fail when the CONTAINER_SCAN tool is included in a Detect run (i.e.included in the DetectToolsFilter). The behavior should be as follows:
detect.container.scan.file.path
was not provided, Detect should skip container scan without publishing a failure.detect.container.scan.file.path
was provided, however the path was empty, an invalid path/URL was provided or the image could not be resolved/downloaded, Detect should publish a failure for CONTAINER_SCAN. Resolves IDETECT-4078Thanks to @dterrysynopsys - the BlackDuck version checking code sections are already implemented in the #955 draft and implemented in the same way in this PR to be re-used.
JIRA
IDETECT-4076
IDETECT-4078