enumeray connector member

Inspect and manage connector co-admin membership.

Use when: Review responsibility for one connector or deliberately add/remove a co-admin.

Role and prerequisites: Connector owner or current co-admin; transfer and membership changes are owner-only. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray connector member list lab-connector

Every command also accepts the profile, API, JSON and timeout options.

Choose a subcommand

Command	Purpose
list	Inspect a connector’s owner, co-admins and governance generation.
add	Add a connector co-admin at an observed generation.
remove	Remove a connector co-admin at an observed generation.

Result and next step

Choose a subcommand below. Membership changes require the owner and the observed ownership generation.

Inspect connector get and its context, grant and audit records before changing authority.

Exact syntax, defaults and accepted values

Inspect co-administrators; owner changes use the ownership generation

Usage: enumeray connector member [OPTIONS] <COMMAND>

Commands:
  list    Inspect the owner, co-administrators and ownership generation
  add     Add a co-administrator using the observed ownership generation
  remove  Remove a co-administrator without revoking independent compute grants
  help    Print this message or the help of the given subcommand(s)

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help