Skip to content

Remove the legacy resource routes, tables and services #9492

Open

Description

@bobbai00

Task Summary

While the kinds move (#9489), their old routes stay as adapters and their old tables stay as read-only views, so the current frontend keeps working. This task ends that period.

  1. Clients. The frontend and the agent service call the generated client (Define the resource service's API in one contract and generate code from it #9485) instead of the old routes.
  2. Old routes and tables. Once nothing calls a legacy route or reads a view, both are removed, together with the per-kind access and sharing code. Old ids stay only as a mapping to rid.
  3. Services. config-service and access-control-service fold into the resource service, so there are fewer services to deploy.

Discussion points

  1. The Angular frontend: move its resource calls to the generated client now, or keep the old routes until the React frontend (Proposal: Ditch Angular and Switch to a new frontend framework #9387) replaces it. Moving Angular is work that will be thrown away, while waiting keeps the adapters longer.
  2. Old ids: links to a workflow or a dataset carry today's ids and live in bookmarks, emails and papers, and stored result paths carry workflow and execution ids. The mapping to rid keeps both working, for example with a redirect for links.
  3. Callers outside the repository: scripts that call the API directly need a deprecation notice, and a release in which both the old and the new routes work.

Done when no legacy resource route, view or per-kind table remains, and the frontend and the agent service call only the generated client.

Task Type

  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other

Activity

  1. added theissue type on Nov 16, 2026
  2. changed the title [-]Remove the legacy resource routes and tables[/-] [+]Remove the legacy resource routes, tables and services[/+] on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions