enumeray connector ownership accept

Accept a connector ownership transfer addressed to your account.

Use when: The owner provided an active transfer proposal for this connector.

Role and prerequisites: Named transfer recipient. 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 accept lab-connector 33333333-3333-4333-8333-333333333333

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 of the proposed transfer; the transfer ID identifies the stored proposal.
<TRANSFER_ID>	Ownership-transfer ID returned by model transfer or connector ownership transfer. Only the named recipient can accept it.

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

Result and next step

Accepts the exact connector transfer addressed to your account if the original ownership generation remains valid. Existing compute grants and immutable execution identities remain unchanged.

Inspect connector member list/get and review existing co-admins and grants.

Exact syntax, defaults and accepted values

Accept a transfer only for the explicitly selected connector

Usage: enumeray connector ownership accept [OPTIONS] <ID> <TRANSFER_ID>

Arguments:
  <ID>           Stable connector ID from connector list/get
  <TRANSFER_ID>  Ownership-transfer ID returned by the transfer proposal; only its recipient may accept

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