Raw REST methods¶
Most users never need these. They exist so the compound methods
(tags.create(attached_zone=...), nodes.release(...),
users.create(..., project_role=...), …) have a stable lower layer.
_raw methods correspond 1:1 to REST calls. They do not perform any
compound logic — no zone cascade on tag delete, no association close
on node release, no project-access binding on user create. Calling
_raw puts the burden of correctness on you.
The escape-hatch surface¶
| Method | What it does | Compound replacement |
|---|---|---|
tags.create_raw(name, **fields) |
POST /trackable_objects only |
tags.create(...) |
tags.update_raw(uid, **fields) |
PUT /trackable_objects/{uid} only |
tags.update(...) |
tags.delete_raw(uid) |
DELETE /trackable_objects/{uid} only — no zone cascade |
tags.delete(uid) |
tags.replace_groups(uid, group_uids) |
PUT /trackable_objects/{uid}/groups with bare-array body |
— |
tags.bulk_delete(uids) |
Loop delete_raw, continue-on-error |
— |
zones.create_raw(name, **fields) |
POST /zones only — no dynamic-binding |
zones.create(...) |
zones.update_raw(uid, **fields) |
PUT /zones/{uid} only |
zones.update(...) |
zones.delete_raw(uid) |
DELETE /zones/{uid} only — no detach |
zones.delete(uid) |
groups.delete_raw(uid) |
DELETE /groups/{uid} only — leaves stale memberships |
groups.delete(uid) |
nodes.delete_raw(uid) |
DELETE /nodes/{uid} — fail-fast (not bulk) |
nodes.delete(uid) (continue-on-error) |
nodes.assign_raw(...) |
POST /nodes_associations/assign |
— |
nodes.release_raw(...) |
POST /nodes_associations/release — does NOT close associations |
nodes.release(...) |
associations.bulk_create_raw(pairs) |
Loop create, continue-on-error |
associations.bulk_create(...) |
users.create_raw(email, password) |
POST /users only — no project-role binding |
users.create(..., project_role=...) |
users.update_raw(uid, **fields) |
PUT /users/{uid} only |
users.update(uid, project_role=...) |
users.change_password_raw(uid, ...) |
PUT /users/changePassword — leaves SDK with stale token |
auth.change_password(...) |
If your use case calls one of these directly, consider whether the compound replacement would do the right thing more safely.