enumeray connector context preflight-status

Read the latest host check without initiating another.

Use when: Inspect current readiness, historical evidence, expiry or corrective roles.

Role and prerequisites: Connector owner or current co-admin with connectors:read. 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 preflight-status lab-connector lab-cpu

Inputs and options

Input	Meaning and use
<CONNECTOR>	Stable connector ID from connector list/get. Owning a model does not grant connector administration.
<CONTEXT>	Registered execution-context ID belonging to the selected connector; use connector context list to inspect it.

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

Result and next step

Shows the attempt and report, validity and host readiness. Passed history becomes stale when its report, contact, credential, ownership or process session is no longer current. Successful retrieval exits 0 independently of readiness.

Resume an existing operation or request a fresh check explicitly after corrections.

Exact syntax, defaults and accepted values

Read the latest host-check attempt/report without initiating a check

Usage: enumeray connector context preflight-status [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