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.
9. Module host and service state
module_host composes independently described service modules. The catalogue
registers identity, Resource Manager, deployments, Storage, Key Vault, App
Configuration, Event Grid, DNS, PostgreSQL, MySQL, managed Redis, Log
Analytics, Application Insights, Service Bus, Functions and App Service. Shared
identity is exposed through separate Entra, RBAC, managed-identity and Windows
LDAP frontend modules. --modules can restrict startup; dependency validation
and lifecycle operations determine which combinations are usable.
A module declares routes and required/provided capabilities. Authentication, resource groups, provider inventory/lifecycle, DNS names, workspace access and service diagnostics cross module boundaries through capabilities. Shared state exposed by a capability must outlive its consumers; do not return a dangling pointer into a destructed module.
Request and lifecycle flow
- The host establishes trace context, validates/splits routing inputs and chooses the best matching route.
- Management routes authenticate through the identity capability. Data planes apply their own token/key/SAS rules.
- An in-flight reference protects the selected module while its handler runs; host-table locks are not held across service work.
- The provider validates version/schema, synchronizes its own state and emits the Azure-compatible response/error shape.
- The host adds correlation/diagnostic accounting. Transport completion is observed separately after socket transfer.
Unload stops admission and waits for in-flight calls; dependent modules prevent unsafe removal. State is retained. Resource-group deletion is a separate provider lifecycle operation and cascades data removal, including native engine deletion. Active deployment work must be quiesced before that deletion can complete.
Persistence and data planes
Private per-module state replaces the old single state file. document_file
provides atomic document updates; provider stores define their own rollback and
schema rules. Blob generations/files, queue documents, secret versions,
configuration revisions, operation records and telemetry rows have distinct
limits and lifetime semantics. Only acknowledged durable changes should be
reported as accepted when the API promises persistence.
Table Storage and the Event Grid delivery outbox use SQLite through the
sqlite_database wrapper (WAL, synchronous=FULL, size caps, bound
parameters only); a write or entity group transaction is one database
transaction. Storage reports blob changes to Event Grid through the optional
event_publisher capability, and Event Grid delivers to queues through the
optional storage_queues capability, so neither module requires the other.
Queue receive/update/delete is serialized so competing consumers cannot claim the same visibility lease. Blob readers hold immutable generations. Key Vault and App Configuration values remain development data stored without an at-rest encryption service. Monitoring bounds persistence and rejects unsupported query syntax instead of inventing results.
Protocol references: host/API (source checkout required), modules (source checkout required), Storage (source checkout required), Queues (source checkout required), Tables (source checkout required), Event Grid (source checkout required), Key Vault (source checkout required), App Configuration (source checkout required), monitoring (source checkout required).
Directory, scoped permissions and workload identities
Identity owns the shared directory capability, backed by private JSON for legacy
installations or dedicated PostgreSQL when configured. entra_directory,
azure_rbac, managed_identities and windows_ldap are separate frontends over
that authority. They can have independent admission/lifecycles without duplicating
users, groups, credentials or role assignments. LDAP requires PostgreSQL and the
optional socket/frontend processes; a loaded module alone is not an LDAP server.
Bootstrap credentials retain administrator status. New applications, principals and users start without resource permissions. The host guards supported ARM operations; Service Bus separately checks sending and receiving/settlement. App-role claims and resource RBAC are distinct: an API role does not grant ARM administration. Each data plane retains its own implemented authorization boundary.
Functions consumes the workload identity capability and exposes public identity attachments in ARM. Its runtime mailbox carries the private header; the helper injects it with the HTTPS App Service identity endpoint. App settings and public inventory omit the credential. The endpoint authenticates the workload and selects only an attached principal. System identity lifecycle follows its owner; user-assigned identity has an independent ARM resource.
The interactive login service keeps bounded, process-local form tickets, codes and rotating refresh grants. The HTML form uses a strict CSP with the validated callback origin allowed for its post-login redirect. Code redemption checks S256 PKCE, callback, client and scopes. Users' passwords use salted PBKDF2; ID tokens are explicitly separated from API access tokens. Read the identity reference (source checkout required) and implementation plan (source checkout required) before extending the contract.
The directory IPC chapter follows the exact PostgreSQL session, migration marker and slapd/Unix-socket path. The persistence chapter explains file replacement and embedded SQLite separately; there is no single shared database for all modules.