Available Flags
| Flag | Default | Env Var |
|---|---|---|
--config string | $HOME/.suprsend.yaml | – |
-h, --help | – | – |
-n, --no-color | Disabled | NO_COLOR |
-o, --output string | pretty | – |
-s, --service-token string | – | SUPRSEND_SERVICE_TOKEN |
-v, --verbosity string | info | – |
-w, --workspace string | staging | – |
Syntax and Example Usage
—config
stringPath to configuration file. This is where your profiles and global settings will be saved. Defaults to
$HOME/.suprsend.yaml.
—help, -h
Show help information for any command.—no-color, -n
By default, output is colored.You can disable colors when piping results to scripts, log files, or CI systems where ANSI codes may cause issues. This can also be set globally via the
NO_COLOR environment variable.
—output, -o
stringDefault -
pretty. Output format:
pretty, yaml, or json.Use
json or yaml when piping results to other tools or scripts, and pretty for human-friendly interactive use.
—service-token, -s
stringFor locally overriding the authentication token.
It is not recommended to use this flag in scripts or CI systems, since it will be visible in shell history or process listings. Instead, use profile or set as environment variable
SUPRSEND_SERVICE_TOKEN.
—verbosity, -v
stringDefault -
info.Log level (in increasing order of severity):
debug < info < warn < error < fatal < panic. Each level includes logs from all levels below it. Use higher levels like
warn or error in scripts for cleaner logs, and debug during troubleshooting to see detailed request and response information.
—workspace, -w
stringTarget workspace for commands. Defaults to
staging.