Skip to main content

Admin v2 Route Compatibility Plan

Status​

superseded — see docs/adr/ADR-009-multi-brand-domain-routed-isolation.md and servers_v2/admin_service/tests/test_legacy_routes_removed.py.

The plan no longer reflects current state: the /v2/* surface has been removed, not restored. The companion spec at docs/specs/migrations/2026-04-22-admin-v2-route-compatibility.md was already marked superseded; this plan was missed in that pass and is brought into alignment here. Legacy callers must migrate to /api/v1/* on servers_v2/admin_service. The Phase 1 / Phase 2 checklists below describe work that was either completed and later reversed by the route-deletion decision, or no longer applicable.

Date​

  • Drafted: 2026-04-22
  • Superseded: 2026-05-05

Spec​

  • docs/specs/migrations/2026-04-22-admin-v2-route-compatibility.md (also superseded)

Original Goal (no longer being pursued)​

Incrementally restore the legacy admin_server v2 route surface on servers_v2/admin_service without regressing the current /api/v1/* admin edge.

Phase 1​

  • add a dedicated /v2 compatibility router in admin_service
  • re-mount the low-risk exact-prefix resource families under /v2
  • add verb/path aliases for historical PATCH and plural routes where the current implementation already exists
  • add selected player action aliases for the historical /players/{id}/actions/* paths
  • add compatibility tests for route registration and representative alias execution

Phase 2​

  • restore the highest-traffic legacy resource families in the /v2 compatibility router: player-groups, player-tags, player-notices, player-messages, player-deposits/actions/*, player-withdrawals/actions/*, player-rollings, player-registrations, agent-settings, agent-announcements, agent-notices, promotions, coupons, deposit-events, attendance-events, register-events, providers, message-templates, site-maintenance
  • expand compatibility tests to cover representative legacy resource paths
  • close the remaining route-family gaps listed in the spec: agents, agent-withdrawals, meta
  • add route-by-route inventory tests against the old admin_server v2 surface
  • review payload-shape drift for every aliased endpoint
  • review semantic drift for site-maintenance and other upload-backed resources
  • update migration readiness when the remaining semantic-review items are closed