enumeray connector context get

Inspect one execution context’s lifecycle, generation and retirement readiness.

Use when: You need the source generation or operational blockers before replacing, reopening or retiring a context.

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

Inputs and options

Input	Meaning and use
<CONNECTOR>	Owning connector ID from connector list/get.
<CONTEXT>	Source context ID from connector context list. Its generation is separate from ownership and connector configuration generations.

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

Result and next step

Returns active/draining/retired state, chosen replacement and accepted-work policy, context work, configuration retirement and acknowledgement evidence, and separate connector-wide work and local-cleanup status.

Plan replacement or investigate the reported work and delivery obligations. Local journal inspection remains necessary before host cleanup.

Exact syntax, defaults and accepted values

Inspect context lifecycle, retained work and retirement readiness

Usage: enumeray connector context get [OPTIONS] <CONNECTOR> <CONTEXT>

Arguments:
  <CONNECTOR>  Owning connector ID from connector list/get
  <CONTEXT>    Execution-context ID registered under the selected connector

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