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
Unify backend resource management around one schema, one API contract and one access check #9483
This implements #9395: every kind of resource (workflows, datasets, models, computing units, environments and warehouses) follows one definition, so creating, versioning and sharing a resource are written once instead of once per kind. The work has five parts:
Schema (Adjust the database schema for unified resource management #9484). Add tables for resources, versions, access and lineage next to today's tables, and keep them in step with today's tables until each kind moves. Every deployment applies schema updates by itself.
Cleanup (Remove the legacy resource routes, tables and services #9492). Once the frontend and the agent service use the new API, remove the old routes, tables and per-kind code, and fold config-service and access-control-service into the resource service.
The order: #9484 and #9486 first, in parallel, then #9485 once the schema is agreed. #9489 needs all three, and #9492 comes last. Today's code keeps working at every step, because each kind has one source of truth at a time and the other side follows it: by triggers before the kind moves, and by read-only views after.
For background, see #9395 and #3749. Related: #5423 moves the Dashboard Service to Dropwizard 4.
Activity