stado service directory connect
Invocation
stado service directory connect [OPTIONS] <NAME>Purpose
A usable route to one service, derived from where it is placed. There is no other address. If the service is placed somewhere that does not answer, that is what this says -- resolving to something local instead is how a caller ends up talking to a process nobody placed. A route through an adapter this host's resolver already holds a connection on, unanswered longer than the refresh interval it declares, is refused with that connection's sentence instead of knocked on: the knock would stand behind it for as long as it stands (`stado resolver status`).
Required inputs and options
| Input or option | Contract |
|---|---|
<NAME> | Service name as the directory keys it, e.g. `brama` |
--target <TARGET> | Resolve as this target instead of this machine |
--consumer <CONSUMER> | Which declared consumer is calling. Selects among this machine's resolver adapters when a service is bound once per consumer |
--no-verify | Report the address without proving anything answers there |
--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
- 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.