enumeray connector preflight

Check host prerequisites locally without a model publication.

Use when: Host preparation needs diagnosis before starting the connector service.

Role and prerequisites: Intended connector OS account. Review and prepare the host first. Development requires explicit --allow-development-execution each time.

Example

enumeray connector preflight --plan host-plan/plan.json

Inputs and options

Input	Meaning and use
--plan <PLAN>	Generated private plan.json, readable by the intended connector account. It never supplies development consent implicitly.
--allow-development-execution	Explicit host consent for trusted same-user process/direct development contexts. Required on every launch-capable invocation. Managed identity separation remains enforced; model code can access this OS user’s connector credentials and files.

Host commands use explicit connector credentials or the private journal and emit JSON results; compute-runner uses only its stdin protocol and directory. User profile and API override options do not apply.

Result and next step

Returns a structured report without user profiles or API calls. Exit 0 means required host checks passed; 1 means blocked or unverified. Checks submit no scientific or Slurm jobs and clean only their private probes.

Follow each correction with the named responsible role; repeat after fixing prerequisites.

Exact syntax, defaults and accepted values

Check host prerequisites locally, without profiles or model publications

Usage: enumeray connector preflight [OPTIONS] --plan <PLAN>

Options:
      --api <API>                    User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --plan <PLAN>                  Generated host-plan.json to check without applying or repairing it
      --allow-development-execution  Explicit consent for trusted same-user process/direct checks
      --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