opschain properties reset
Included from Basic tier
opschain properties reset [--project | --env <code> [--asset <code>]]
Drops a target node's database property layer back to empty, written as a
new version — history and per-step pins are retained, so the repo's
committed properties files alone define the next run, and nothing a running
step pinned is disturbed. Repo-scoped: it runs in the repository and has no
remote form. Use opschain properties export first if the layer holds
values worth keeping.
Flags
| Flag | Meaning |
|---|---|
--project | Target the project layer (the default). |
--env <code> | Target an environment layer. |
--asset <code> | Target an asset layer (requires --env). |
Output
opschain properties reset --env dev
/projects/demo/environments/dev: DB property layer reset as version 3 (history and per-step pins retained)
With -o json / -o yaml, a document with node_path and new_version
fields.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Reset. |
| 1 | The reset failed (unreadable store, unresolvable target). |
| 2 | Usage error. |
Named errors
--project and --env are mutually exclusive(exit 2).--asset requires --env(exit 2).resetting properties is repo-scoped and runs locally — it has no remote form; run it in the repository (or pass --local)— a server target is active (exit 1).
See also
opschain docs cli/properties-export— promote the layer into the repo file instead of dropping it.opschain learn 1.3— properties and settings, guided.