Skip to content

retry failed scass signature scan #1496

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

Merged
merged 5 commits into from
Aug 1, 2025

Conversation

dterrybd
Copy link
Contributor

If a user has not allowed the SCASS IPs we want to retry the SCASS scan using the previous approach. I originally tried pushing down a lot of data to do this but it's easier, and I think cleaner, to just bubble back up to the start and being a new scan without the --scass-scan argument.

spyRunner.runSignatureScannerOnline(detectRunUuid, projectNameVersion, dockerTargetData, scanIdsToWaitFor,
gson);

verify(spyRunner, times(2)).executeScan(any(), any(), any(), any(), any(), anyBoolean(), anyBoolean());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a similar test that doesn't throw exception and verifies that the call is made only once is worthwhile in addition to this one?

@dterrybd dterrybd merged commit 610e7eb into master Aug 1, 2025
@dterrybd dterrybd deleted the dev/dterry/IDETECT-4781-retry-failed-scass-sig branch August 1, 2025 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants