Polling an Update Host

This command allows you to track the progress of an update host flow.

Example: bright-cli entrypoints:update-host-polling [options] <jobId>

General options

Option

Description

--config

Path to the file with configuration

--log-level

What level of logs to report. Any logs of a higher level than the setting are shown. [choices: 0, 1, 2, 3, 4, 5, "silent", "error", "warn", "notice", "verbose", "trace"]

  • Default*: --log-level 3

--hostname

Bright application name (domain name).

  • Default*: --hostname app.brightsec.com

--proxy=socksProxyUrl

Specify a proxy URL to route all traffic through. This should be an HTTP(S), SOCKS4, or SOCKS5 URL.
Can be read also from environment param PROXY.

  • Default*: If you specify SOCKS://<URL>, then SOCKS5h is applied.

--proxy-bright

Specify a proxy URL to route the traffic to Bright.

--proxy-target

Specify a proxy URL to route the traffic to the targets.

--timeout

Request timeout in seconds or a duration string (e.g. 10s, 1m, 1h, 10h, 1y).

  • Default*: --timeout 30

--insecure

Allows CLI to proceed and operate even for server connections otherwise considered insecure.

  • Default*: --insecure false

-a, --archive

A collection of your app's http/web sockets logs into HAR file. Usually you can use browser dev tools or our browser web extension

--token=apiKey, -t=apiKey

The unique identifier used to authenticate a user. The token (API key) can be issued in your organization’s dashboard.
Required option.

Update Host options

OptionDescription
--project, -pAllows specifying the Bright project for a scan using the project ID. You can find the project ID in the Projects section in the Bright app.