opschain templates version
templates
Manages a template's versions. Each version pins a revision (branch, tag or commit) of the template's Git remote, and assets pinned to a version take their action catalog from that revision. Two independent lifecycle flags guard a version:
- locked — the pinned revision and metadata are read-only until unlocked; a locked (or archived) version only accepts its own unlock/unarchive.
- archived — the version stops being assignable to assets.
On top of those, writes that would move assets are refused while assets are pinned to the version, unless the in-use override is passed — see each verb's page.
| Subcommand | Does | Manual |
|---|---|---|
upsert | Create a version, or repin/re-describe/fetch an existing one | opschain docs cli/templates-version-upsert |
lock | Make the version read-only | opschain docs cli/templates-version-lock |
unlock | Lift the lock | opschain docs cli/templates-version-unlock |
archive | Stop the version being assignable | opschain docs cli/templates-version-archive |
browse | List the tree at the version's sealed commit, one directory at a time | opschain docs cli/templates-version-browse |
cat | Print one text file at the version's sealed commit | opschain docs cli/templates-version-cat |
unarchive | Make it assignable again | opschain docs cli/templates-version-unarchive |
See also
opschain docs cli/templates-assign— pin assets to a version.opschain docs cli/templates-show— every version's state at a glance.