Skip to main content
Version: v5.6.1

opschain admin runner-group list

Included from Basic tier

opschain admin runner-group list

Lists the runner groups (the v2 RunnerService.ListRunnerGroups RPC) with each group's placement contract: the exclusive flag, its registered key=value attributes, its node-path bindings and whether a group-wide drain is in force.

Flags​

FlagMeaning
--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 group rows as a machine document (including the description and timestamps the table omits) instead of the table.

Output​

NAME EXCLUSIVE ATTRIBUTES DRAINING
default false - false
secure true location=dc1,network=sec false

(The table also carries a BINDINGS column, the comma-joined node-path bindings, between ATTRIBUTES and DRAINING.)

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-group-set — create or change a group's contract.
  • opschain docs cli/admin-runners-list — the runners enrolled in these groups.
  • opschain docs fleet-queue — how attributes, bindings and exclusivity decide placement.