Anchorage API reference
    Preparing search index...
    interface ProvisionDeploymentOptions {
        backend: ProvisioningBackend;
        clock?: () => number;
        finalizedStateProvider?: FinalizedOrdinaryStateProvider;
        initialExecutionFenceState: "open" | "migration-locked";
        routeAttestation?: AttestConvergedActiveRouteOptions;
        secrets: DeploymentSecrets;
        spec: DeploymentSpec;
        store: FleetStateStore;
    }
    Index

    Properties

    clock?: () => number
    finalizedStateProvider?: FinalizedOrdinaryStateProvider
    initialExecutionFenceState: "open" | "migration-locked"

    The execution-fence state this deployment is born in. REQUIRED; no default.

    It lives on the OPTIONS and deliberately not on DeploymentSpec. The spec is the digested canonical description of a deployment (deploymentSpecDigest), and every stored record, drift audit, and migration decision compares against that digest — adding a field to it would change the digest of every deployment already in the fleet and present as fleet-wide drift, scheduling migrations for artifacts nobody touched.

    It is also provisioning-time-only by nature: after the first pass the fence is live operational state an operator moves through POST /admin/execution-fence, so migrateFleet, rollbackExternalRelease and decommissionDeployment neither take it nor need it — re-seeding is INSERT-if-absent and can only ever repair a missing row.

    Tuning for the convergence wait the ready-commit attestation performs. The defaults suit every provider this package targets.