Veillax/Hammerhead
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 17 Wiki Activity

Clarify delete cascade in API notes

Browse Source
This commit is contained in:
Veillax committed 2026-10-27 16:54:23 -06:00
1 parent 1c2a5b71bd
commit 8f3d303d7b
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
docs/api-automation.md
+1 -1
View File
@@ -33,4 +33,4 @@ level, and a server key has no user, so `/api/me` and other per-user routes refu
- Keys are all-powerful within their scope (no read-only or per-resource scopes), and have no expiry. - Keys are all-powerful within their scope (no read-only or per-resource scopes), and have no expiry.
- `PUT` on ports replaces the whole object; omitted fields reset. - `PUT` on ports replaces the whole object; omitted fields reset.
- Site tokens are returned on create and, for admins, in `state`. - Site tokens are returned on create and, for admins, in `state`.
- Deleting an edge/site does not check for ports that use it (the server cleans up or refuses; clients should order deletes). - Deleting an edge or site cascades silently (its ports and domains go with it, as do ports left with no target), so Terraform plans should not rely on dependent resources surviving.