Hetzner Cloud: reads checked against a live project
Inspect on a real project showed servers, snapshots, primary IPs and prices answer as the reader expects; volumes, load balancers, floating IPs and certificates were seen only as empty lists. Docs and the adapter's header say so; no code change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a91efcbfe2
commit
730d7fb36e
2 files changed
+3
-3
No files matched your search
@@ -5,8 +5,8 @@
|
||||
* snapshots and backups, its primary and floating IPs, its load balancers (and the health of their targets), its certificates (and when they expire) and Hetzner's price list — enough to say
|
||||
* what is off, what is close to its traffic quota, what has no recent backup, what is unhealthy or about to expire, and roughly what the project costs. Nothing is sent to Hetzner but GET requests for these; no server is started, stopped or changed.
|
||||
*
|
||||
* Endpoints and field names are from Hetzner's published OpenAPI file (`/servers`, `/volumes`, `/images`, `/primary_ips`, `/pricing`; lists are paged, 50 at a time) and have not been
|
||||
* checked against a live project here; every field is read defensively. A token belongs to one project, so one integration is one project. The API allows 3600 requests an hour per project.
|
||||
* Endpoints and field names are from Hetzner's published OpenAPI file (`/servers`, `/volumes`, `/images`, `/primary_ips`, `/pricing`; lists are paged, 50 at a time) and were checked against a
|
||||
* live project (servers, snapshots, primary IPs and prices; volumes, load balancers, floating IPs and certificates only as empty lists); every field is read defensively. A token belongs to one project, so one integration is one project. The API allows 3600 requests an hour per project.
|
||||
*/
|
||||
import { requestJson } from "../httpJson.js";
|
||||
import { withDiagLogging } from "../../services/diagLog.js";
|
||||
|
||||
Reference in new issue
Block a user