opschain admin platform status
Included from Basic tier
Shows each plane's emergency posture and the halt/resume history — the v2
PlatformService.GetPlatformPosture read, printed as the server's document (JSON, or YAML
under -o yaml). This is where the active posture row ids live: a resume
must name the row it lifts, and this verb is how you find it when the halt's
own output is gone.
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Posture fetched. |
| 1 | Request failed or the token was rejected. |
| 2 | Usage error — no server/credential resolvable. |
Named errors
a server is required — pass --server <url>, set OPSCHAIN_SERVER, or 'opschain context use <name>'— exit 2.this command needs a login or an admin token — run 'opschain login', pass --auth-token, set OPSCHAIN_ADMIN_TOKEN, or store one with 'opschain admin login'— exit 2.the server rejected the credential — run 'opschain login' again, or check the admin token— HTTP 401 (exit 1).
Examples
opschain admin platform status
See also
opschain docs cli/admin-platform-haltandopschain docs cli/admin-platform-resume— the verbs this status feeds.