Skip to main content
Every command accepts the flags below. They can appear anywhere in the invocation.

​
Targeting

Which account, environment, and endpoint the command talks to. See Authentication for how these resolve against each other and against stored profiles.
A key passed with --api-key does not identify a region on its own. Pair it with --region or --base-url, or the command stops and tells you rather than guessing.

​
Output

How results are formatted and how much commentary you get. Colour is also disabled automatically when NO_COLOR is set, when TERM=dumb, and whenever stderr is not a terminal — so CI logs stay clean without passing anything.

​
Pagination

For bulk export, combine --output json with --limit rather than reaching for --all — --all prints only the final page, which is rarely what an export wants.

​
Automation

--no-input is what you want in a non-interactive environment where a hung prompt would stall the job: instead of waiting for an answer nobody can give, the command fails immediately and tells you which flag would have supplied it.

​
Informational

​
Not global: --force

--force skips the confirmation prompt on destructive actions, but it is declared per command, not on the root. It has to come after the resource and action:
Passing it earlier makes the CLI read the resource name as the flag’s value and report a confusing error about the action instead.

​
Next steps

Output & scripting

Exit codes and the stdout/stderr contract.

Authentication

Profiles, regions, and credential precedence.