fix(web): route Mission Control API calls through orchestrator proxy #747
Reference in New Issue
Block a user
Delete Branch "fix/mission-control-proxy-routes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Mission Control components called
/api/mission-control/*→mosaic-api.woltje.com(404, wrong service). These routes live on the orchestrator service and must go through the Next.js server-side proxy.Fix
New: Catch-all proxy at
/api/orchestrator/[...path]/route.ts— forwards any method toORCHESTRATOR_URL/<path>withORCHESTRATOR_API_KEYinjected server-side.Updated: All Mission Control components now call
/api/orchestrator/api/mission-control/*instead of/api/mission-control/*.Components fixed:
GlobalAgentRoster,AuditLogDrawer,PanelControls,KillAllDialog,BargeInInput+ their tests.