quinzee.cloud

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.

Administrator’s guide

3. Understand modules and their dependencies

A module is a service implementation loaded inside quinzee.cloud. A provider is the module's ARM-facing resource interface. A capability is a typed service that another module requires, such as authentication or the shared directory. An external helper is a separate process. These are four different boundaries.

Step 1: read the module inventory

Open Emulator → Modules. Inspect each module's loaded state, what it provides, what it requires and which loaded modules depend on it. The table below follows the running catalogue rather than inferring dependencies from names.

Module ID Family Required modules Data/process dependency
identity Shared None Private JSON, or dedicated PostgreSQL when configured
entra_directory azure identity Shared directory; no second database
azure_rbac azure identity Shared directory
managed_identities azure identity Shared directory
windows_ldap Windows identity Shared PostgreSQL plus optional external OpenLDAP
resource_manager control-plane identity Private durable JSON
deployments control-plane identity, resource_manager Private history and in-process operations
storage resource-provider identity, resource_manager Blob files, queue persistence, embedded SQLite for tables
key_vault resource-provider identity, resource_manager Private durable secret/version files
app_configuration resource-provider identity, resource_manager Private durable settings/revisions
log_analytics resource-provider identity, resource_manager Bounded durable workspace files
application_insights resource-provider identity, log_analytics, resource_manager Component metadata plus Log Analytics workspace
event_grid resource-provider identity, resource_manager Embedded SQLite delivery outbox
postgresql managed-engine identity, resource_manager External PostgreSQL container and labelled data volume
mysql managed-engine identity, resource_manager External MySQL container and labelled data volume
managed_redis managed-engine identity, resource_manager External Valkey container and labelled data volume
service_bus resource-provider identity, resource_manager Embedded SQLite; Proton AMQP listener
functions resource-provider identity, resource_manager Private records and external Docker hosting helper
app_service azure functions Functions shared Microsoft.Web host and runtime
dns infrastructure identity Generated zone/Corefile; separate CoreDNS process

The identity module is retained because administrative APIs need authentication. The shared authority is not the same module as Entra's management frontend. Loading windows_ldap makes its status page available; a PostgreSQL configuration and LDAP socket are still required for actual LDAP service. The application PostgreSQL provider does not automatically supply the directory's PostgreSQL. Keep that dedicated directory backend outside workloads whose management depends on the directory itself.

Loaded module inventory

Step 2: understand optional relationships

Event Grid collects the queue capability at delivery time. StorageQueue delivery therefore needs Storage to be loaded even though it is not a mandatory module dependency. Blob events require the Event Grid event publisher to be available. DNS collects service names from loaded providers. A declaration can load without CoreDNS running, but clients will not resolve names through that external server. The engine modules load without Docker; their servers cannot start without the engine supervisor. App Service requires Functions' hosting capability because one provider owns Microsoft.Web plans, records and dispatch.

Step 3: load only what a lab needs

--modules selects an initial set and loads required dependencies. Unselected modules remain in the catalogue for later loading. To avoid a surprise, inspect the resulting Modules page instead of assuming the command-line list equals the final loaded set. For example, a Storage-only resource lab still needs the shared authority and resource-group provider. Explicit identity frontend lists should name entra_directory, azure_rbac, managed_identities and windows_ldap according to the services you intend to expose.

Step 4: unload in dependency order

  1. Stop active hosted apps or database servers if their processes must stop.
  2. Select the dependent module and unload it. App Service must unload before Functions; Application Insights before Log Analytics.
  3. Check the module's state and any refusal explaining loaded dependants.
  4. Reload and confirm that persisted resources return.

Unloading stops that module's routing/workers while retaining its data. It does not delete resources and does not generally stop external containers. Deleting a resource is different: the provider may enqueue container/volume removal. Never edit a persisted dependency or resource record to force an unload.

Platform facilities that are not extra modules

Health, module management, certificate metadata and operational telemetry are host facilities. There is no separate certificates catalogue module to add to --modules. The generated zone and CoreDNS container belong to the DNS workflow; CoreDNS is not another Azure service module. These distinctions explain why the number of pages, services, containers and module IDs is not the same.