enumeray connector context create

Register a versioned execution-context manifest under a connector.

Use when: An enrolled connector needs an approved direct/SSH process or Slurm execution path.

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 create lab-connector --file process-direct-context.json

For exact JSON shapes and credential references, use execution contexts and manifest envelopes. The manifest connector_id must match the connector supplied on the command line; a mismatch is rejected before a request.

Inputs and options

Input	Meaning and use
<ID>	Connector ID that owns this context.
--file <FILE>	Version-1 execution-context JSON envelope. Start from a context example and replace connector ID and absolute site paths before registration.

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

Result and next step

Validates the execution-context envelope, metadata and execution contract locally, then registers it through the API.

Inspect connector context list and grant the intended author access to the returned context.

Exact syntax, defaults and accepted values

Register a context from a versioned execution-context manifest

Usage: enumeray connector context create [OPTIONS] --file <FILE> <ID>

Arguments:
  <ID>  Stable connector ID from connector list/get

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --file <FILE>        Version-1 execution-context JSON envelope; connector_id must match the selected connector
      --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