stado credentials token sync
Invocation
stado credentials token sync [OPTIONS] --from-host <FROM_HOST> --host <HOST> --source-token-file <SOURCE_TOKEN_FILE> --token-file <TOKEN_FILE> <CONSUMER>Purpose
Deliver an existing bearer between matching declared vault copies, without changing grants
Required inputs and options
| Input or option | Contract |
|---|---|
<CONSUMER> | Positional input; required or optional as shown in the invocation. |
--from-host <FROM_HOST> | Command option; required or optional as shown in the invocation. |
--host <HOST> | Command option; required or optional as shown in the invocation. |
--source-token-file <SOURCE_TOKEN_FILE> | The bearer file on FROM_HOST: a bare name under ~/.stado (the name mint's --token-file-name took), or an absolute or ~/ path inside that account's home |
--token-file <TOKEN_FILE> | The bearer file on HOST, in the same forms as --source-token-file |
--check | Verify the destination without changing its file |
--shared-vault | HOST reads FROM_HOST's vault through its own Skarbiec resolver route; verify the bearer against FROM_HOST's grant, not a local copy. Refused unless the registry declares that route |
--json | Command option; required or optional as shown in the invocation. |
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
- Refused unless the registry declares that route
- 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.