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

8. Administer storage, secrets and configuration

These services are in-process modules. They do not need the external SQL engine supervisor merely to store data. Table Storage uses embedded SQLite; the shared LDAP directory's optional PostgreSQL is unrelated. Back up the complete cloud state consistently instead of trying to substitute an external database.

Step 1: provision a storage account

Open Storage → Storage accounts, select a group and use Create. Enter a globally unique local account name, location, kind and supported SKU. The developer IaC sample uses StorageV2 and Standard_LRS. The provider exposes separate Blob, Queue and Table endpoints under that account. Provision containers/queues/tables through the service APIs or the corresponding QHQ controls; an account alone contains no application objects.

Storage account creation

For Blob workloads, use private containers (publicAccess: None in ARM). Clients control content type, metadata, block IDs, range requests and supported SAS fields through the Blob API. SAS grants are separate from Entra resource roles; restrict their resource, permissions and expiry. Key regeneration changes which account-key signatures remain valid. Account deletion removes its data. There is no Azure Files, page/append Blob, lease or snapshot implementation.

Step 2: inspect queue work without accidentally consuming it

Open Storage → Queues. Select the account and queue. Create/delete queues, send synthetic messages, and use Peek to inspect pending work without changing visibility. A receive gives a message a visibility lease and pop receipt; deletion requires the current receipt. An expired lease makes work visible again, so consumers must tolerate duplicates. Application-level completion and a successful HTTP send are different events. Queue SAS is not implemented.

Queue metadata, message visibility timeout and time-to-live are API values. Do not confuse their duration with the server HTTP timeout. Updating a message changes its receipt; a stale receipt cannot settle it. Before deleting a queue, stop producers and confirm whether pending work is disposable.

Step 3: administer tables as typed data

Open Storage → Tables, select the account and table, then work with entities. Every entity has PartitionKey and RowKey. Use ETags for conditional updates so another writer's change is not silently replaced. Supported types include strings, booleans, numeric values, DateTime, GUID, binary and explicit Int64 encoding. The table API supports its bounded OData filters, paging and same- partition entity group transactions. An ARM table declaration does not create any entities. There is no Table SAS, ACL or service-properties implementation.

Treat SQLite database files and their WAL/SHM files as one live store. Copying only the main file while writers are active is not a consistent backup. The backup chapter's stopped-instance procedure avoids that mistake.

Step 4: operate Key Vault secrets

Open Key Vault → Vaults. Create a vault with name, location, tenant and supported SKU metadata. In Secrets, set a synthetic value, retrieve it through authorized access, then change it and observe a new version. Version metadata can include content type, tags, enabled state, not-before and expiry. Deleting a secret moves it into the soft-deleted workflow; recovery and purge are separate operations. QHQ’s Delete selected performs soft delete followed immediately by purge. Use the secret API/SDK directly when you need a recoverable deletion. Purge is irreversible. A vault resource's Azure-shaped RBAC/access-policy fields do not implement the full Azure Key Vault authorization model locally.

Quinzee stores secrets and versions privately but does not claim blanket at-rest encryption. Do not put real production credentials into a development screenshot or public deployment output. Cryptographic keys and certificate objects are not implemented by this module. The host's TLS certificate metadata is a separate platform function.

Step 5: operate App Configuration

Open App Configuration → Configuration stores, create a store and select Key-values. Enter the key, optional label, value and content type. Labels select separate variants; an absent label and a named label are not interchangeable. Use ETags for concurrent edits. Lock a value when it should become read-only, and deliberately unlock it before changing it. Revisions retain prior values according to the implemented service workflow. Deleting the store deletes its configuration history.

A Key Vault reference is a JSON setting with the expected content type and URI; it does not make the configuration service fetch or authorize that secret for your application. The application resolves it using its own secret client. Snapshots, replicas and full feature-management behavior are not implemented.

Configuration choices at these boundaries

Surface Values an operator/application controls
Storage ARM Account name/location/tags, supported kind/SKU; container privacy, queue metadata, table name
Blob data Object name/content/type/metadata, staged blocks, conditions, supported SAS scope/permissions/expiry
Queue data Queue name/metadata, message content, visibility and TTL, pop-receipt-based settlement
Table data Table name, partition/row keys, typed properties, ETag conditions, bounded filters/paging
Vault ARM Name/location/tags, tenant/SKU and retained Azure-shaped properties; do not assume policy enforcement from metadata
Secret data Name/value, version attributes, content type/tags, enabled/not-before/expiry, delete/recover/purge
Configuration ARM Name/location/tags and supported SKU/properties
Key-values Key/label/value/content type/tags, ETag conditions, lock/unlock

Choose concrete values and plan for fixed limits

Storage account names use 3–24 lowercase letters/digits. Accepted kind values are StorageV2, Storage, BlobStorage, BlockBlobStorage and FileStorage; the name FileStorage does not enable Azure Files. Accepted SKUs are Standard_LRS, Standard_GRS, Standard_RAGRS, Standard_ZRS, Standard_GZRS, Standard_RAGZRS, Premium_LRS and Premium_ZRS. These describe metadata, not replicated disks or a performance guarantee. supportsHttpsTrafficOnly: false is rejected. The accepted accessTier values are Hot (default) and Cool; they are metadata, not different local storage engines. Archive storage is unsupported. Service properties such as Blob retention/CORS are not tunable merely because a PUT is accepted. Container public access is refused.

Boundary Value or fixed bound
Blob request At most 256 MiB upload body; staged commit at most 1 GiB
Blob listing maxresults at most 5,000
Blob SAS Resource b/c, ordered r/w/d/l permissions, UTC start/expiry, HTTPS only; account-key signatures
Queue receive 1–32 messages; positive visibility up to seven days
Queue enqueue Initial visibility may be zero; TTL defaults to seven days, positive seconds or -1 for no expiry
Queue payload 64 KiB message text including any Base64 expansion; 8 KiB metadata
Queue capacity 1,024 queues/account, 1,024 messages/queue, 16 MiB serialized queue file; listing at most 5,000
Table query $top 1–1,000; at most 15 filter comparisons, nesting 32, filter text 16 KiB
Table entities 252 custom properties; key at most 1 KiB UTF-16 without slash/backslash/#/?/controls; string/binary value 64 KiB; entity 1 MiB
Table transactions 1–100 operations in one table/partition; 4 MiB batch, 2 MiB ordinary request
Table capacity 1,000 tables/account; 4 GiB total table data per emulator; continuation also after 5,000 examined rows or 16 MiB loaded data
Vault 3–24-character unique name; matching local tenantId; standard/premium SKU
Secret 1–127 letters/digits/hyphens, case-insensitive; value at most 25 KiB; 500 versions retained
Secret attributes enabled is enforced; not-before and expiry are retained metadata and do not prevent retrieval
Configuration store 5–50 letters/digits/hyphen/underscore; free/developer/standard/premium SKU
Configuration authentication disableLocalAuth rejects HMAC; otherwise two read-write and two read-only keys, each individually regenerable
Configuration data Key plus value at most 10 KiB; last 1,000 revisions/store; lists are one page

App Configuration accepts keys containing / (URL-encode it), an optional label, content type and tags. Key/label filters support comma lists and trailing *; \0 selects the null label. If-Match/If-None-Match enforce conditional changes. Read-only keys cannot mutate values; disabling local auth does not disable bearer access. Regenerating one key invalidates that key's old signatures. Vault access-policy and enableRbacAuthorization fields are retained but are not an enforced per-principal data-plane ACL. Storage data-plane RBAC is likewise not implemented. These token data planes retain bootstrap/administrator access; new scoped identities are refused until service-specific authorization exists. An ARM Reader assignment does not grant access to their contents. Shared keys and supported SAS have their own authorization rules. Some older providers retain additional Azure metadata; retention of a field is not proof that its operational behavior is emulated. Do not edit private JSON/SQLite files to invent an unsupported feature.