enumeray connector get

Inspect connector identity, maintenance, execution authority, capacity and generation.

Use when: You need the observed generation or to distinguish desired configuration from reported readiness.

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 get lab-connector

Inputs and options

Input	Meaning and use
<ID>	Existing connector ID from connector list.

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

Result and next step

Prints owner identity, ownership_generation and connector configuration generation alongside lifecycle and capacity; credential secrets remain private.

Use configure, maintenance/resume or withdraw-authority/restore-authority for changes; inspect diagnostics for retained work.

Exact syntax, defaults and accepted values

Inspect connector registration, capacity and current configuration

Usage: enumeray connector get [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