enumeray connector member remove

Remove a connector co-admin at an observed generation.

Use when: An account should stop managing this connector and inspecting its operational run metadata.

Role and prerequisites: Resource owner; co-admin status alone does not grant ownership changes. 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
enumeray connector member remove lab-connector --user 11111111-1111-4111-8111-111111111111 --generation 1

Resource names and UUIDs below are examples. Replace them with IDs returned by your service; --generation 1 is valid only if the latest response reports generation 1. 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>	Connector ID you own.
--user <USER>	Stable UUID of the target account, obtained from auth whoami for yourself or from the service administrator for another account. Display labels and email addresses are not user IDs.
--generation <GENERATION>	Observed ownership_generation from connector get or generation from connector member list. Configuration or context generations cannot guard ownership changes.

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

Result and next step

Removes the named membership. This is separate from revoking its compute grants or login credentials.

Inspect members and the new resource generation before another management change.

Exact syntax, defaults and accepted values

Remove a co-administrator without revoking independent compute grants

Usage: enumeray connector member remove [OPTIONS] --user <USER> --generation <GENERATION> <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
      --user <USER>              Stable UUID of the target account; use auth whoami to find your own ID
      --generation <GENERATION>  Observed ownership generation; independent of execution 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