Version: v5.7.0

opschain templates version browse

templates

opschain templates version browse <project>/<code> --version <v> [path]

Lists the tree at a template version's sealed commit, one directory at a time — the repository root when no path is given — the CLI twin of the GUI's Browse on the template version page. It answers "what does this version actually contain" without a clone, and it shows exactly what a workflow's content() / list() read could see as you (opschain docs expressions, "content() and list()"): a file is readable only where your identity holds read on the repository-content rule path /git/content/projects/<project>/<path>, and a directory lists only when something readable sits beneath it. Symbolic links and submodules list by kind and are never followed.

Output

acme/web_tier @ 1.2.0 (4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d)
NAME        KIND  SIZE  READABLE
deploy/     dir   -     true
README.md   file  812   true
Makefile    file  2048  false

-o json|yaml prints {commit, path, entries: [{path, name, kind, size, readable}]}.

Flags

Flag	Meaning
`--version <v>`	The version to browse (required).

Exit codes

Code	Meaning
0	Listed (an empty directory, or one with nothing readable, prints `no readable entries here`).
1	The template or version was not found, the version has not resolved its commit yet, or the server refused the read.
2	Usage error — missing `--version`, malformed address, no server target.

Output​

Flags​

Exit codes​

See also​

Output

Flags

Exit codes

See also