Skip to main content

bootstrap_deployment_process

Function bootstrap_deployment_process 

Source
pub async fn bootstrap_deployment_process(
    signing_key: SigningKey,
    service_token: Option<String>,
    trust_source: DeploymentTrustSource,
    remote_node: bool,
    network_required: bool,
    records: &RdsConfig,
) -> Result<()>
Expand description

Atomically consume the explicitly selected deployment witness and install the process Discovery resolver. Selection never falls back between the OS-owned and DID-anchored providers.

remote_node selects how the DID-anchored provider reaches Discovery:

  • false (same-node fabric, e.g. the metal stack’s service start --ipc containers sharing the IPC volume): a lazy local discovery client — identical posture to the OS-owned path, which also never pings. This is required on nodes that HOST Discovery (possibly as an in-process dependency started after this install), where a pre-install network liveness check would self-deadlock.
  • true (remote worker): dial the DID-advertised network transport and REQUIRE a successful signed liveness ping before installing — a dead or wrong-key endpoint refuses the boot.

service_token is the caller’s own enrolled, signer-bound credential. Discovery must not borrow another service’s credential or infer MAC clearance from a key.