stado service declare
Invocation
stado service declare [OPTIONS] --file <FILE>Purpose
Declare a service against the fleet's one contract. Stado ships no list of services: a service is whatever its author declares — an immutable source the bytes come from, a run spec the unit is rendered from, how the service is observed, and who may call it. This command writes that declaration into the service directory; `deploy` then needs no flags beyond the name, because everything it would ask for is already written down.
Required inputs and options
| Input or option | Contract |
|---|---|
--file <FILE> | Path to the declaration file (JSON). Required keys: `name`, `host`, `source.artifact`, `source.sha256`. Optional: `run`, `verify`, `consumers`, `endpoints`, or `port` as a shorthand for one loopback endpoint on the declared host |
--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
- Required keys: `name`, `host`, `source.artifact`, `source.sha256`.
- 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.