stado doctor
Invocation
stado doctor [OPTIONS]Purpose
Ordered deployment preflight: config, storage, provider auth, quota, release channel, agent template, VM identity, registry, queue pause state and alert channels. Exits non-zero if any check FAILs
Required inputs and options
| Input or option | Contract |
|---|---|
--json | Emit the full machine-readable report instead of the table. The JSON always carries every remedy, so `--fix-hints` adds nothing to it |
--fix-hints | Also print the governing env var or command for checks that PASS, not only for the ones that need fixing |
--deployment-preflight | Gate deployment prerequisites only. Fleet-wide service placement is still reported by ordinary `stado doctor`, but does not block installing an unrelated Stado control-plane release |
--release-verification | Verify only that the exact public release coordinate is served after deployment |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.