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.

Developer’s guide

9. Manage settings with App Configuration

App Configuration stores application settings by key and label. The label lets Book:Queue have different values for development and another environment. A null label is distinct from a label named development.

Keep nonsecret settings here, such as a queue name. Put passwords in Key Vault. A feature flag can be represented as a setting, but this emulator does not provide a separate server-side feature-management system.

Step 1: set, read and enumerate settings

Replace Program.cs with:

using Azure.Data.AppConfiguration;

var book = BookContext.Load();
var outputs = book.Outputs();
var configuration = new ConfigurationClient(
    new Uri(outputs["configurationEndpoint"]), book.Credential);
await configuration.SetConfigurationSettingAsync("Book:Queue", "book-work", "development");
await configuration.SetConfigurationSettingAsync("Book:Document", "hello.txt", "development");

var selected = await configuration.GetConfigurationSettingAsync("Book:Queue", "development");
Console.WriteLine($"Worker queue: {selected.Value.Value}");
var selector = new SettingSelector { KeyFilter = "Book:*", LabelFilter = "development" };
await foreach (var setting in configuration.GetConfigurationSettingsAsync(selector))
    Console.WriteLine($"{setting.Key} [{setting.Label}] = {setting.Value}");

Run dotnet run --no-restore. Expect Worker queue: book-work and the two Book: settings. Rerunning updates those same key/label pairs. Retrieving Book:Queue without a label would address the null-labelled setting instead.

Step 2: handle concurrent changes

Settings have ETags. Use conditional updates when you must preserve another writer's changes; an ETag mismatch returns 412. Read-only settings reject writes with 409 until unlocked. QHQ's configuration page can list, set and delete settings with an optional label.

The local store retains the last 1,000 revisions. Revision history is useful for inspection, but snapshots and point-in-time reads are not supported. The combined key and value size limit is 10 KB. Lists currently return their results in one page rather than implementing Azure's continuation paging.

Step 3: choose an authentication method

The example uses a bearer credential. App Configuration also accepts its connection-string HMAC authentication; listKeys returns read-write and read-only keys. A read-only key cannot write. Setting disableLocalAuth on the store disables those key-based requests.

Do not put an access-key connection string in a browser bundle or print it in logs. This tutorial's .NET backend retrieves settings; the browser receives only the information the application deliberately exposes. Neither local labels nor a stored Azure RBAC property isolate tenants or applications.