Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
11. Deployments and native engines
The deployment module preflights bounded inline ARM templates, resolves a supported expression/dependency subset, and schedules resource operations in dependency order. It dispatches through authenticated public provider routes; it does not write another provider's private state. Microsoft's pinned Bicep compiler remains an external tool that produces the ARM JSON input.
Deployment history and operation records survive restart. Secure parameter values and credentials do not become a replay log. Interrupted active deployments are explicitly failed on restart, while already-created resources remain for an incremental retry. Group deletion quiesces deployment work so a late task cannot recreate a supposedly deleted resource.
The managed-engine providers store desired state and submit schema-validated
mailbox requests through engine_runtime. The separate Python supervisor
reconciles pinned PostgreSQL, MySQL and Valkey containers, private volumes,
certificates and native readiness. Cloud reads status and publishes actual engine
IPs through DNS; resource existence alone is not readiness.
The supervisor owns CA keys outside the cloud data mount. Public CA/CRL material allows native clients to retain chain, hostname and revocation checks. Docker operations are limited to validated schemas and labelled owned resources; ARM input cannot supply arbitrary images or executable commands.
New desired revisions carry optional W3C context into the mailbox. The helper emits fixed operation spans/logs, plus a heartbeat independent of slow provisioning work. Diagnostic engine states are last-reconciled state; freshness comes from the heartbeat, not an assumption that a recorded Running instance must still be available.
The precise APIs, expression limits, deletion semantics, image identities and
operator commands are in provisioning notes (source checkout required).
Ownership/recovery checks are in tests/engines/; the ordinary CTest suite uses
contract tests, while the native-engine/application targets exercise real
protocol servers.