opschain admin packs install
Included from Basic tier
Uploads a signed pack bundle and installs it as one immutable (pack, version) in the platform's pack store. The server verifies the bundle offline against its embedded keyring before anything is stored, and each failure refuses by name:
- bad signature — the manifest signature does not verify;
- digest mismatch — a file's content does not match its signed digest;
- unknown signing key
<key_id>— the bundle is signed with a key this build does not trust (a released binary trusts production keys only; a development build also trusts the development key); - missing entitlement — the manifest requires a
packs:<name>entitlement the licence does not grant; - platform too old — the manifest's minimum platform version is newer
than this server. Only a released build is placed against the floor: a
development build (a git describe past a tag, such as
v5.6.0-26-g2e99304e, or a dirty build) carries code its tag does not and is never refused on this ground; - version already installed with different content — versions are immutable; publish a new version instead.
Re-uploading an installed version with identical content is idempotent and reports it as already installed.
opschain admin packs install -f opschain-pack-infrastructure_v1.2.3.bundle
Installed opschain-pack-infrastructure version 1.2.3 (24 files, signed by 2026-test)
-o, --output json|yaml emits the installed version row.
Flags
| Flag | Meaning |
|---|---|
-f, --file <path> | The signed .bundle file to upload (required). |
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
See also
opschain docs cli/admin-packs— the family overview and packs.yaml form.opschain docs cli/admin-packs-pin— steering unversioned resolution.