Repair router frontdoor route boundaries and service prefixes
This commit is contained in:
@@ -133,6 +133,12 @@ First-party Stella APIs are expected to flow through router transport; reverse p
|
||||
external/bootstrap surfaces that cannot participate in router registration yet (for example OIDC browser
|
||||
flows, Rekor, and static/platform bootstrap assets).
|
||||
|
||||
The local route table also carries a small set of explicit precedence rules that must stay ahead of the
|
||||
generic `^/api/v1/{service}` matcher. Platform-owned surfaces such as `/api/v1/aoc/*` and
|
||||
`/api/v1/administration/*` resolve directly to `platform`, and browser compatibility prefixes such as
|
||||
`/doctor/*` and `/scheduler/*` strip the frontdoor prefix before dispatch so the target services still
|
||||
receive their canonical `/api/v1/doctor/*` and `/api/v1/scheduler/*` paths.
|
||||
|
||||
```bash
|
||||
# Default frontdoor route table
|
||||
ROUTER_GATEWAY_CONFIG=./router-gateway-local.json \
|
||||
|
||||
Reference in New Issue
Block a user