Files
marketplaces/docs/architecture/foundation/adr/ADR-004-configuration-bootstrap-and-provider-abstraction.md

12 lines
1.1 KiB
Markdown
Raw Normal View History

# ADR-004: Configuration Bootstrap and Provider Abstraction
2026-07-19 15:28:35 +04:00
Status: Superseded
Date: 2026-07-03
2026-07-19 15:28:35 +04:00
Superseded by: `docs/backend/BACKEND-INTEGRATION.md` §4 (Bootstrap) and §14 (Backend replacement pattern)
2026-07-19 15:28:35 +04:00
## Original decision (preserved for history)
2026-07-19 15:28:35 +04:00
Configuration must initially come from mock JSON and later from backend API without changing consumers. `ConfigService` is the only configuration entrypoint; consumers depend on typed selectors only; provider implementation is swappable (`MockBootstrapProvider` / `ApiBootstrapProvider`); the frontend calls `GET /bootstrap` when the API provider is enabled and never passes a tenant id.
2026-07-19 15:28:35 +04:00
This decision remains in effect. The full, verified contract — endpoint, caching, field-by-field DTO reference, and the generalized mock↔API provider-swap pattern this ADR introduced (now used by every admin domain, not just bootstrap) — lives in `docs/backend/BACKEND-INTEGRATION.md`. Read that document for current, code-verified detail; this file is kept only so ADR-numbered references in `docs/architecture/foundation/README.md` continue to resolve.