Instance / Config Properties

Per‑tenant configuration is expressed through the layered config‑override model rather than a static per‑instance properties document:

  • Layers (OverrideLayer): business → store → service, deep‑merged (later layers win) into an effective config (GET …/effective-config).
  • Sections that can be overridden: endpoints, authentication, settings, metadata, rateLimiting, additionalHeaders, featureFlags, and serviceInstanceMap (maps a consuming service name → that service’s instance id; validated against app.supportedServices, required before enabling — SERVICE_INSTANCE_MAP_REQUIRED).
  • Payment and notification per‑store configuration are persisted inside config_overrides at the store layer (payment secrets are encrypted at rest).

A separate “instance” concept exists in the codebase (an instances collection plus a tenant‑context step) but its CRUD API is not currently enabled (§4).

Revision History
2026-08-05 | JP – Created the page and added the content.