enumeray connector member list

Inspect a connector’s owner, co-admins and governance generation.

Use when: You need to review management authority or obtain the generation for a membership change.

Role and prerequisites: Connector owner or current co-admin. 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

Use ownership_generation from connector get or generation from connector member list for owner-only changes; it is independent of connector configuration generation.

Inputs and options

Input	Meaning and use
<ID>	Managed connector ID.

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

Result and next step

Prints ownership/membership metadata; compute grantees are a separate inventory.

Use connector member add/remove only with the observed generation.

Exact syntax, defaults and accepted values

Inspect the owner, co-administrators and ownership generation

Usage: enumeray connector member list [OPTIONS] <ID>

Arguments:
  <ID>  Stable connector ID from connector list/get

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