enumeray connector context preflight

Request or resume an owner-scoped host check before publication.

Use when: An enrolled running connector should inspect a registered context through the real host transport.

Role and prerequisites: Connector owner or current co-admin with me:read, connectors:read and connectors:manage. 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 lab-connector lab-cpu --directory check-operation

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.
--directory <DIRECTORY>	Private saved check operation. Repeating it retains the same request identity and original API/account/context.
--interval <INTERVAL>	Polling interval in seconds, 1–60; default 2.
--deadline <DEADLINE>	Wait deadline in seconds, 1–3600; default 300. The server attempt expires after 15 minutes.

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

Result and next step

Saves API/account/context and request identity before requesting the check. Repeating the directory reconciles the same attempt. Reports stay on stdout; exit 0 means current host prerequisites passed, 1 means blocked/inconclusive, 5 is a local wait deadline and 130 is interruption.

Resolve reported corrections and use a new directory for a deliberately fresh check; keep uncertain operations for reconciliation.

Exact syntax, defaults and accepted values

Request/resume a publication-independent host check using a saved identity

Usage: enumeray connector context preflight [OPTIONS] --directory <DIRECTORY> <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
      --directory <DIRECTORY>  Private saved check operation; reuse after interruption to reconcile the same request
      --interval <INTERVAL>    Host-check polling interval in seconds (1-60) [default: 2]
      --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
      --deadline <DEADLINE>    Local check wait budget in seconds (1-3600); expiry leaves the saved attempt available [default: 300]
      --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