tokens, webhooks, logs and more
Reference for the operational commands: tokens, webhooks, logs, inspect, config, migrate, login and init.
tokens
sextant tokens create --name ci-deploy --scope jobs:write --expires-in 90d
sextant tokens list
sextant tokens revoke tok_71c0de
sextant tokens bootstrap --config sextant.tomlcreate takes --scope more than once. bootstrap talks to the store directly, so it works when you have lost every token; run it on the server with the same config. Scopes are listed in Tokens and scopes.
webhooks
sextant webhooks create https://hooks.example.com/sextant --events job.failed,job.dead
sextant webhooks list
sextant webhooks test whk_5d02ab
sextant webhooks delete whk_5d02abSee Webhooks for events and signatures.
logs
Streams structured logs from the server over HTTP, so you do not need access to its container.
sextant logs --follow --queue emails --level warn --since 10minfo inspect
Prints a job with its full attempt timeline. See Observability for sample output.
sextant inspect job_8f3k2m9q
sextant inspect job_8f3k2m9q --output-lines 200 # show more of each attempt's outputconfig
sextant config check --config sextant.toml
sextant config print --config sextant.tomlcheck validates the file and exits 2 on errors, so it belongs in CI. print shows the effective configuration after defaults, environment variables and flags are applied, with secrets masked.
migrate
sextant migrate up --config sextant.toml # apply store migrations
sextant migrate status --config sextant.toml # list applied and pending
sextant migrate config --from sextant.yaml --to sextant.toml
sextant migrate from-v1 --redis redis://localhost:6379/0 --dry-runfrom-v1 is covered in Migrating from v1.
login and init
sextant login --url <url> --name <profile> asks for a token (input is hidden) and saves the profile. sextant init writes a commented starter sextant.toml; it refuses to overwrite an existing file unless you pass --force.