enumeray connector context

Manage execution contexts for one connector.

Use when: Register immutable execution definitions, inspect readiness and coordinate replacement.

Role and prerequisites: Connector owner or current co-admin; transfer and membership changes are owner-only. 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 list lab-connector

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

Choose a subcommand

Command	Purpose
preflight	Request or resume an owner-scoped host check before publication.
preflight-status	Read the latest host check without initiating another.
list	List a connector’s registered execution contexts.
create	Register a versioned execution-context manifest under a connector.
update	Change an execution context’s descriptive location and data disclosure.
get	Inspect one execution context’s lifecycle, generation and retirement readiness.
replacement-plan	Inspect paginated replacement dependencies and actions with responsible roles.
cutover	Close a context to new use and choose how accepted queued work drains.
reopen	Reopen a draining context for future eligible use.
release-configurations	Request retirement of obsolete publication configuration on a draining context.
retire	Permanently archive a draining context after its retirement blockers clear.
wait-retirement	Observe a draining context until work, delivery and configuration retirement settle.

Result and next step

Choose a subcommand below; each context retains its own stable ID and generation.

Inspect connector get and its context, grant and audit records before changing authority.

Exact syntax, defaults and accepted values

Register and manage this connector's execution contexts

Usage: enumeray connector context [OPTIONS] <COMMAND>

Commands:
  preflight               Request/resume a publication-independent host check using a saved identity
  preflight-status        Read the latest host-check attempt/report without initiating a check
  list                    List execution contexts visible under this connector
  create                  Register a context from a versioned execution-context manifest
  update                  Change descriptive location and data-access disclosure
  get                     Inspect context lifecycle, retained work and retirement readiness
  replacement-plan        Inspect replacement dependencies and actions for connector owners and authors
  cutover                 Close new work and explicitly drain or cancel queued runs
  reopen                  Reopen future operations while retaining cancellations and configuration releases
  release-configurations  Request retirement of obsolete publication configuration on a draining context
  retire                  Permanently archive a context after work, delivery and configuration finish
  wait-retirement         Wait for context retirement readiness without shutting down the connector
  help                    Print this message or the help of the given subcommand(s)

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