enumeray connector publish-log-archives

Publish retained terminal diagnostic archives without scientific execution.

Use when: Completed work has a local archive pending upload and you need to retry archive publication.

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 publish-log-archives --journal ./local-journal --token-file ./connector-state/token

If a prior one-shot process left an unclosed session, establish stopped ownership before adding --confirm-prior-process-stopped. Keep the same journal and archive evidence.

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.
--token-file <TOKEN_FILE>	Private regular file containing only the connector bearer token, typically the token file written by enroll. One-shot commands read a token from stdin if omitted.
--confirm-prior-process-stopped	Explicit recovery assertion that the journal’s previous process stopped on every host, including out-of-band processes. Establish this externally before using the flag; it is not a backend cancellation command.

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

Retries retained archive reservation/transfer/publication independently of science results. An unavailable/expired archive does not authorize scientific execution again.

Inspect run log-archive and download the diagnostic artifact if it becomes available.

Exact syntax, defaults and accepted values

Publish retained terminal log archives without executing scientific work

Usage: enumeray connector publish-log-archives [OPTIONS] --journal <JOURNAL>

Options:
      --api <API>                      User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --journal <JOURNAL>              Existing private durable journal retaining the terminal archive and delivery evidence
      --profile <PROFILE>              Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --token-file <TOKEN_FILE>        Private regular file containing the connector bearer token; omit to read token text from stdin
      --config <CONFIG>                Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --confirm-prior-process-stopped  Assert that the journal's previous process stopped on every host before recovery
      --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