enumeray connector ownership transfer

Propose a connector ownership transfer to another account.

Use when: Responsibility for connector governance is moving to a new owner.

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 ownership transfer lab-connector --to 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.
--to <TO>	UUID of the proposed new owner. The target must separately accept the returned ownership-transfer ID before ownership changes.
--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

Creates a transfer proposal and ID; ownership stays with the proposer until the recipient accepts.

Give the returned transfer ID to the named recipient; they use connector ownership accept.

Exact syntax, defaults and accepted values

Propose transfer to a named recipient using the ownership generation

Usage: enumeray connector ownership transfer [OPTIONS] --to <TO> --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
      --to <TO>                  Stable UUID of the proposed owner, who must separately accept the transfer
      --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