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
feat: create db users via namespace-qualified id, drop namespace arg
The server no longer accepts a separate `namespace` field when creating a DB
user; the namespace is now derived from a namespace-qualified id of the form
"<namespace>:<user>" passed in the URL path (weaviate PR #11501,
resolveUserKeyForCreate). Update the client to match:
- users.db.create: remove the `namespace` parameter; always POST an empty body.
The (optionally qualified) id is already carried in the path. Drop the
now-unused 1.38 version guard tied to the namespace field.
- sync/async .pyi stubs: update the create signature accordingly.
- UserDB.namespace and get/list parsing are unchanged: the server still returns
`namespace` in the user response for global operators (handlers_db_users.go).
Tests:
- mock_tests: replace the namespace-in-body tests with
test_users_db_create_qualified_user_id_goes_in_path (asserts the qualified id
lands in the URL path and the body stays empty) and
test_users_db_create_posts_empty_body. These pin the wire contract and are the
version-independent regression guard.
- integration: create the namespaced user with the qualified id directly.
- Bump WEAVIATE_138 to 1.38.0-rc.0-b9ea106, the first build containing PR #11501.
Verified: mock + unit suites pass (34); 8/9 namespace integration tests pass
against a live cluster. The qualified-create integration test requires the
b9ea106 image, which was still publishing to Docker Hub at commit time; the
server source at b9ea106 is git-verified to implement this contract and CI runs
the live check.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments