cnos spec
cnos spec
cnos spec manages manifest-global config specification entries stored under schema: in .cnos/cnos.yml.
Use cnos define, cnos value set, and cnos secret set for concrete config values and secret refs.
Commands
cnos spec listcnos spec show value.server.portcnos spec set value.server.port --type number --required --summary "HTTP server port"cnos spec delete value.legacy.flagcnos spec doctorlist
cnos spec listcnos spec list --prefix value.server.show
cnos spec show value.server.portcnos spec show value.server.port --jsonset
cnos spec set supports two modes:
- Non-interactive: pass one or more field flags.
- Interactive: no field flags in a TTY.
Examples:
cnos spec set value.server.port --type number --required --summary "HTTP server port"cnos spec set value.app.stage --enum '["local","stage","prod"]'cnos spec set value.legacy.flag --clear-deprecatedField flags use JSON-first parsing for --default, --example, and --enum.
For secret.* keys, --default, --example, and --enum are rejected to avoid plaintext secret material in the manifest.
delete
cnos spec delete value.legacy.flagcnos spec remove value.legacy.flag --jsondoctor
cnos spec doctorcnos spec doctor --jsoncnos spec doctor --fill-missingcnos spec doctor --review-all--fill-missing and --review-all are interactive write modes. They currently:
- require a TTY,
- require a writable local root (remote roots are read-only),
- reject
--json.