stado service declare
Invocation
stado service declare [OPTIONS] --file <FILE>Purpose
Declare a service against the fleet's one contract. Writes source, run spec, observation and consumer declarations into the service directory so `deploy` can use them without repeating its inputs.
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. `answer_seconds` is retired and refused: a resolver never cuts a relayed request by a clock |
--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`.
- `answer_seconds` is retired and refused: a resolver never cuts a relayed request by a clock
- 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.