Epic 8 — IDAM extension and build/deploy
GitHub issue: #280
Catalog: Epics 1–9 | Theme: IDAM (Epics 6–9)
Overview
Support IDAM core + extension: (1) merge reference core and customer extension OpenAPI at build time so a single IDAM service serves both; (2) document path conventions and ingress rules for the two-service deployment option (core + extension on two ports, ingress path-based routing).
Scope
- Merged spec: Generator or manual step merges
idam-core.openapi.yaml and customer idam-extension.openapi.yaml into one combined spec; BRRTRouter codegen on combined spec → single IDAM binary.
- Path conventions: Document core vs extension path prefixes so ingress rules (for two-service option) are unambiguous (see IDAM Design: Core and Extension §4.2).
Stories
References
Epic 8 — IDAM extension and build/deploy
GitHub issue: #280
Catalog: Epics 1–9 | Theme: IDAM (Epics 6–9)
Overview
Support IDAM core + extension: (1) merge reference core and customer extension OpenAPI at build time so a single IDAM service serves both; (2) document path conventions and ingress rules for the two-service deployment option (core + extension on two ports, ingress path-based routing).
Scope
idam-core.openapi.yamland customeridam-extension.openapi.yamlinto one combined spec; BRRTRouter codegen on combined spec → single IDAM binary.Stories
References