opschain metadata set
Included from Basic tier
opschain metadata set <node-path> <field>=<value> ...
Writes field values on one node (MetadataService.SetNodeMetadata). Each
value is typed by its field's profile schema before it is sent: bool
fields take true/false, integer and duration fields a decimal integer
(duration values are seconds), everything else text — an enum value must
be one of the profile's declared values, a date YYYY-MM-DD. Unknown
fields are refused by the server by name (declare it in a profile first). The write needs the metadata-writer determination on
/metadata<node path>; writing a protective field (e.g.
core.criticality) additionally requires a stepped-up session, and the
refusal carries the CLI elevation hint. Every write is audited with
per-field before/after.
-o json / -o yaml emit the node's refreshed own values.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The values were written; the refreshed own-values table follows. |
| 1 | Refused — no metadata-writer determination, an unelevated protective write, an unknown field, or a value outside the field's schema. |
| 2 | Usage error — a malformed <field>=<value> pair, a non-boolean/non-integer value for a typed field, or a missing server target. |