Checking Scan Status

This command configures ongoing polling of a scan status, and helps you follow its progress during CI/CD flows: bright-cli scan:polling [options] <scanId>.

<scanId> is an ID of a scan that you want to poll its status.

After a scan launches, it frequently checks the scan status. If the scan finds at least one issue of, Bright CLI finishes with exit code 50. The breakpoint condition can be cutomized.

Options

Option, alias	Description
`--breakpoint=any/ medium_issue/high_issue/critical_issue`, `-b=any/medium_issue/high_issue/critical_issue`	A conditional breakpoint that finishes the process with exit code `50` only after fulfilling the predefined condition. The breakpoint option allows you to follow the fail-fast principle when polling the scan results. Default: `--breakpoint any`
`--interval=milliseconds`	The period of time between the end of a timeout period or the completion of a scan status request, and the next request for status. For example, 60, 2min, 10h, or 7d. A numeric value is interpreted in milliseconds. Default: `--interval 5000`

Option, alias

Description

--breakpoint=any/ medium_issue/high_issue/critical_issue, -b=any/medium_issue/high_issue/critical_issue

A conditional breakpoint that finishes the process with exit code 50 only after fulfilling the predefined condition. The breakpoint option allows you to follow the fail-fast principle when polling the scan results.

Default: --breakpoint any

--interval=milliseconds

The period of time between the end of a timeout period or the completion of a scan status request, and the next request for status. For example, 60, 2min, 10h, or 7d. A numeric value is interpreted in milliseconds.

Default: --interval 5000

Updated 3 months ago