enumeray connector init

Initialize a one-shot journal bound to a connector and API origin.

Use when: You are qualifying a local connector or deliberately using the one-shot diagnostic workflow.

Role and prerequisites: Connector host operator. Install enumeray on the execution control host. Retain its private journal on durable storage; keep one process owner and the matching connector credential. See recovery rules before taking over retained state.

Example

enumeray connector init --journal ./local-journal --api-base-url http://127.0.0.1:8080 --connector-id lab-worker

The example assumes a local API on port 8080 and an existing connector ID. Do not use init to bypass retained journal recovery or to clone an active connector.

Inputs and options

Input	Meaning and use
--journal <JOURNAL>	Private durable journal directory. Reuse the same path after restart and never copy it to create another active connector. It contains ownership and backend execution evidence.
--api-base-url <API_BASE_URL>	Enumeray API origin. Use HTTPS, or loopback HTTP for local testing; enrollment/run can explicitly allow a trusted private HTTP network. A retained identity is bound to its original origin.
--connector-id <CONNECTOR_ID>	Enrolled connector ID created by enumeray connector create. It must match the token and retained journal.

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

Creates private journal identity and origin binding. It neither enrolls credentials nor claims work; this command accepts HTTPS or loopback HTTP origins.

Supply the matching connector token to claim-once, then execute-once; use enroll/run for service operation.

Exact syntax, defaults and accepted values

Create a one-shot journal bound to one connector and an HTTPS or loopback HTTP API

Usage: enumeray connector init [OPTIONS] --journal <JOURNAL> --api-base-url <API_BASE_URL> --connector-id <CONNECTOR_ID>

Options:
      --api <API>                    User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --journal <JOURNAL>            New private durable journal directory; never clone an active connector's journal
      --api-base-url <API_BASE_URL>  API origin using HTTPS or loopback HTTP; retained identity stays bound to this origin
      --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
      --connector-id <CONNECTOR_ID>  Stable connector ID matching the enrollment credential and intended journal
      --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