opschain templates
templates
Manages a project's templates and template versions: where asset actions
come from. A template pins one of the project's Git remotes; each of its
versions pins a revision (branch, tag or commit) of that remote's
repository, and assets pinned to a version take their action catalog from
that revision. Templates live on the server — every subcommand needs a
server target (--server <url>, OPSCHAIN_SERVER or the active
opschain context) — and are addressed as <project>/<code>.
| Subcommand | Does | Manual |
|---|---|---|
list <project> | List a project's templates | opschain docs cli/templates-list |
show <project>/<code> | Show a template and its versions | opschain docs cli/templates-show |
create <project> | Create a template, optionally with its first version | opschain docs cli/templates-create |
version … | Upsert, lock, unlock, archive, unarchive versions | opschain docs cli/templates-version |
assign <project>/<code> | Repin assets to a version | opschain docs cli/templates-assign |
re-resolve --pack <name> | Cut re-resolved versions for every template using an installed pack | opschain docs cli/templates-re-resolve |
See also
opschain docs cli/git-remotes— the repositories templates build from.opschain learn 3.3— the guided tour of Git remotes and templates.