opschain admin trust assignments
packs:agents
opschain admin trust assignments [--server <url>] [--auth-token <token>]
Lists every assets-under-management assignment
(the v2 TrustService.ListTrustAssignments read), fleet-wide: which agent (by
service-account principal) manages which node-path subtree, with the
creating administrator, timestamp and note. Each row's ID is what
opschain admin trust unassign takes. For one agent's slice of the same
data, opschain admin agent assignments filters by agent id.
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL. Default: the active context, then 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 for that server. |
Output
Always a machine document (JSON unless -o yaml): {"assignments": […]}.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The assignments were printed. |
| 1 | The server refused or failed the request (including a rejected admin token). |
| 2 | Usage — unexpected arguments, or no server / admin token resolvable. |
Named errors
a server is required — pass --server <url>, set OPSCHAIN_SERVER, or 'opschain context use <name>'— exit 2.this command needs a login or an admin token — run 'opschain login', pass --auth-token, set OPSCHAIN_ADMIN_TOKEN, or store one with 'opschain admin login'— exit 2.the server rejected the credential — run 'opschain login' again, or check the admin token— exit 1.
See also
opschain docs cli/admin-trust-assign— create an assignment.opschain docs cli/admin-trust-unassign— remove one.opschain docs cli/admin-agent-assignments— one agent's assignments.