stado service env-show
Invocation
stado service env-show [OPTIONS] --host <HOST> --env-file <ENV_FILE> <NAME>Purpose
Read a managed service's owner-controlled env file, duplicates and all. The counterpart of `env-set`: same approved encrypted channel, same `$HOME` confinement, opposite direction. `service env` answers what the UNIT FILE declares; this answers what the file a launcher `.`-sources declares, which on this fleet is where the interesting values live. Every assignment is listed in FILE ORDER with its line number, and a key assigned twice is reported twice — `effective` for the last assignment, `shadowed` for every earlier one — because a sourced file assigns top to bottom and a later duplicate silently wins. A value whose key looks like a credential is withheld, and a URL carrying userinfo is withheld whatever its key is called. An endpoint, a port, a flag or a `$REFERENCE` is shown whatever its key is called: those are what an operator reads this file to verify. The decision is made ON THE HOST, so a withheld value never crosses the channel.
Required inputs and options
| Input or option | Contract |
|---|---|
<NAME> | Service whose host-local process reads the environment |
--host <HOST> | The single registry host to read |
--env-file <ENV_FILE> | Environment file on the target, absolute or rooted at $HOME |
--reveal <REVEAL> | Show this one variable's value in full, whatever its name suggests. The key name travels; no secret is ever placed in a remote command line either way |
--json | Command option; required or optional as shown in the invocation. |
Output and state effect
This is an inspection/reporting operation. It emits the result described above and does not change managed state unless an explicit option in this page says otherwise. Pass `--json` when the command exposes that machine-readable option.
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.