Retesting a Scan
This command re-runs a scan by ID using the same configuration: bright-cli scan:retest [options] <scan id>.
Arguments
| Argument | Description |
|---|---|
<scan id> | The ID of an existing scan that you want to re-run |
Options
| Option | Description |
|---|---|
--token=apiKey, -t=apiKey | The unique identifier used to authenticate a user. The token (API key) can be issued in your organization’s dashboard. |
--config=pathToConfig | Specifies the path to the configuration file. By default, the CLI tries to discover the config in the package.json in the root directory of your application or a separate file by a specified name in the working directory. For details, see Configuration Files for more information. |
| Allows setting the level of logs to report. Any logs of a higher level than the one specified are shown. The options to select : 0, 1, 2, 3, 4, "silent", "error", "warn", "notice", and "verbose".
|
--cluster | Bright cluster (domain name).
|
--insecure | Allows the Bright CLI to proceed and operate even if the server connection is considered insecure. |
--proxy=socksProxyUrl | SOCKS URL to proxy all traffic.
|
--api=clusterUrl |
|
Updated 16 days ago