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
{{ message }}
Repository navigation
Remove the legacy resource routes, tables and services #9492
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.
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.
Services. config-service and access-control-service fold into the resource service, so there are fewer services to deploy.
Discussion points
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.
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.
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.
Activity
[-]Remove the legacy resource routes and tables[/-][+]Remove the legacy resource routes, tables and services[/+]