opschain admin runner-attributes list
Included from Basic tier
opschain admin runner-attributes list
Lists the registered placement attribute keys and their allowed values
(the v2 RunnerService.ListRunnerAttributes RPC). These keys are the vocabulary of placement:
a runner group may only carry attributes with registered keys, and a run's
placement selectors may only demand them. Every registry starts with the
product-seeded reserved keys location and network, values unrestricted
until an operator enumerates them.
Flags
| Flag | Meaning |
|---|---|
--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. |
--filter <column>[!]=<value> | Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased (spaces/dashes fold to _); * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. Applied client-side. Grammar: opschain docs cli. |
-o json|yaml prints the definitions as a machine document instead of the
table.
Output
KEY ALLOWED VALUES
location dc1,dc2
network (any)
(any) means the key accepts any value until values are enumerated with
opschain admin runner-attributes set.
Exit codes
0 listed; 1 the request failed (network, HTTP error, rejected token); 2 usage.
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-runner-attributes-set— register a key or enumerate its values.opschain docs cli/admin-runner-group-set— where the keys are used.opschain docs fleet-queue— how selectors match group attributes.