start

To review a list of available flags, use the -help or -h flag.

CTS can be run as a daemon in different modes.

Flag: none

Behavior: This is the default mode in which CTS passes through a once-mode phase and then turns into a long-running process. During the once-mode phase, the daemon will exit with a non-zero status if it encounters an error. After successfully passing through once-mode phase, it will begin a long-running process in which errors are logged and exiting is not expected behavior. When the long-running process begins, CTS daemon starts serving API and command requests.

Behavior: CTS will display the proposed state changes for all tasks once and exit. No changes are applied in this mode. On encountering an error before completing, CTS will exit with a non-zero status.

Usage: Intended to be run before long-running mode in order to confirm configuration is accurate and tasks would update network infrastructure as expected.

Flag: -inspect-task [task-name]

Behavior: This has similar behavior as -inspect mode for the selected task. The flag can be specified multiple times to inspect multiple tasks. No changes are applied in this mode.

Flag: -once

Behavior: CTS will run all tasks once with buffer periods disabled and exit. On encountering an error before completing, CTS will exit with a non-zero status.

Usage: Intended to be run before long-running mode in order to confirm configuration is accurate and tasks update network infrastructure as expected.

Options

The start command supports the following options: