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
refactor(BA-5650-I): test and remaining ORM updates
Final slice of the BA-5650 stack split. Contains:
- Remaining ORM touch-ups: models/endpoint/row.py,
models/keypair/row.py, repositories/scheduler/{repository,db_source}.py,
api/adapters/vfolder.py, api/gql_legacy/endpoint.py,
api/gql_legacy/routing.py.
- Test updates that depend on the action/service/DTO renames already
landed in earlier slices: adapter/session, scheduler repositories,
session lifecycle/service, sokovan scheduler suite,
compute_sessions handler, dependency injection tests.
- Autouse ``_user_context`` fixture under
tests/unit/manager/services/session/conftest.py so service tests work
without the auth middleware.
Change the REST v1 session API's delegation mechanism from the `owner_access_key` query parameter to an `owner_id` (user UUID) field. The `owner_access_key` parameter is removed from all session endpoints (`GET /session/{name}`, `DELETE /session/{name}`, `POST /session/_/create-from-template`, `POST /session/_/create`, `POST /session/_/create-cluster`, `GET /session/{name}/logs`, `GET /session/{name}/status-history`, etc.). Clients that previously passed `owner_access_key=<keypair>` to act on behalf of another user must now pass `owner_id=<user uuid>` (and only on the session-creation endpoints; for read/control endpoints the caller always acts as themselves). Session and kernel `access_key` semantics also change: the value is no longer tied to the keypair used to create the session but resolved at read time from the owner's `main_access_key`.
Test updates and remaining ORM/repository touch-ups for the BA-5650 stack: scheduler db_source, keypair and endpoint row cleanup, gql_legacy endpoint/routing, session lifecycle/service tests, sokovan scheduler tests, and dependency-injection tests. No external behavior change beyond what earlier slices documented.
Added in 26.4.1. Create or update the deployment policy for a given deployment (upsert semantics). If the deployment already has a policy, it is replaced entirely with the new configuration
@@ -14933,9 +14923,6 @@ type Routing implements Item
Added in 26.4.1. Create or update the deployment policy for a given deployment (upsert semantics). If the deployment already has a policy, it is replaced entirely with the new configuration
0 commit comments