enumeray setup apply-host

Apply the exact reviewed managed host plan locally as an administrator.

Use when: An approved plan requires account, directory, protected executable, launcher or service preparation.

Role and prerequisites: Host administrator on the selected connector or execution host. Use the matching installed executable and reviewed host digest. Apply copies the approved binary into its protected host path and never reads user profiles.

Example

sudo /path/to/installed/enumeray setup apply-host --plan /absolute/setup/host-plan.json --side connector --approve HOST_PLAN_SHA256 --enrollment-file /absolute/setup/enrollment-0000.json

Inputs and options

Input	Meaning and use
--plan <PLAN>	Generated host plan. Typed actions and the approved digest are revalidated; human instruction text is not executed.
--side <SIDE>	connector prepares its local host, including direct execution; execution prepares the SSH execution host when run locally there.
--approve <APPROVE>	Exact host plan SHA-256 shown by the saved owner setup.
--enrollment-file <ENROLLMENT_FILE>	Optional private one-time document staged only to the connector account. Never supply it to the execution host.
--executable-source <EXECUTABLE_SOURCE>	Local copy of the selected native executable. Connector installation uses executable_sha256; an SSH execution host uses execution_executable_sha256 when supplied.

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

Result and next step

Reuses matching completed operations and preserves conflicts. Enrollment and local preflight use the connector OS account. Service installation requires the plan’s explicit background choice; no service is started.

Review local prerequisite results and start the saved runtime explicitly, then resume the owner setup.

Exact syntax, defaults and accepted values

Apply reviewed managed changes locally as an administrator; never loads a user profile

Usage: enumeray setup apply-host [OPTIONS] --plan <PLAN> --side <SIDE> --approve <APPROVE>

Options:
      --api <API>
          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --plan <PLAN>
          Generated host-plan.json whose typed actions and digest will be revalidated
      --profile <PROFILE>
          Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --side <SIDE>
          Host to prepare locally: connector, or execution for the SSH execution host [possible values: connector, execution]
      --approve <APPROVE>
          Exact host plan SHA-256 from setup review; separate from the owner setup plan digest
      --config <CONFIG>
          Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --enrollment-file <ENROLLMENT_FILE>
          Private one-time enrollment JSON document; supply only on the connector host
      --json
          Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --executable-source <EXECUTABLE_SOURCE>
          Local copy of the reviewed executable on this host; its approved SHA-256 must match
      --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