You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What:
- add a dedicated ProviderProxyHandler for /provider/{id}/... requests
- keep ProjectProxyHandler on its original project-only constructor and flow, and route provider scope through separate wiring
- move provider route registration to explicit /provider/ handlers so static handling does not need provider-specific branching
- rewrite provider route matching as its own router path instead of mixing provider scope into the project-routing control flow
- preserve provider-scoped request propagation from ProviderProxyHandler into ProxyHandler, and keep provider-focused handler/router/e2e/playwright coverage
Why:
- keep provider scope independent from the existing project proxy implementation
- reduce follow-up churn to only the required changes for provider routing
- make provider-scoped matching reviewable as a parallel path instead of a project-routing patch
Tests:
- go test ./internal/handler ./internal/router ./tests/e2e/... (pass)
- MAXX_E2E_BASE_URL=http://127.0.0.1:9880 MAXX_E2E_USERNAME=admin MAXX_E2E_PASSWORD=test123 pnpm --dir tests/e2e/playwright test:provider-proxy-route (pass)
0 commit comments