compute

POST /v1/compute/servers/{serverId}/rebuild

Reinstall a server's operating system.

Всички крайни точки в compute

Всички документи за разработчици

Упълномощаване

Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението sites.view; ключ без него се отхвърля с 403, а не с 404.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

curl -X POST https://api.zinndigital.com/v1/compute/servers/{serverId}/rebuild \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "operating_system": <string>, "confirm": <string> }'

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

⛔⛔ Destructive: everything on the disk is erased and cannot be recovered. The machine comes back on a fresh image, so the answer carries power_state: rebooting and a client polls from there. Three guards, and none of them is optional. The caller needs sites.delete rather than the key that merely spends money — dev may commit the organisation to a billable resource without being trusted to destroy data, so this is deliberately not the key resizeComputeServer uses. The typed confirmation is re-checked server-side, because a dialog a client owns is a dialog an API caller skips: confirm must equal the server's name exactly, compared case-sensitively after surrounding whitespace, and anything else is 422. And the action is audit-logged before the provider is called and left in place whatever happens, because an audit row written only on success leaves no trace of an attempted wipe that errored halfway — precisely the event an investigation is looking for. ⛔ 503 is the expected answer today, and it is honest. No adapter currently advertises rebuild: a usable one needs the provider's own operating-system list, and an OS token we guessed would wipe a customer's machine and reinstall the wrong thing. It is a 503 rather than a 422 because it is our gap, and a customer told "invalid input" for a control nobody wired would retype the same thing for ever. 404 for a server that is not the caller's; 422 for an empty operating_system or a machine that is not active. Requires sites.view and sites.delete.

Параметри

ИмеТипЗадължителноКакво представлява
serverId (path)UuidДаThe server's id, as listComputeServers reports it. Ours (UUIDv7), minted when the order row was written — never the provider's own identifier for the machine.

Тяло на заявката

ИмеТипЗадължителноКакво представлява
operating_systemstringДаWhich image to install, as the provider names it. ⛔ Never a string a screen or a customer composed — an OS token we guessed would wipe the machine and reinstall the wrong thing,…
confirmstringДаThe server's name, typed by the customer. Compared case-sensitively after surrounding whitespace and nothing else, so a client that forgave more would enable the button on…

Отговор

ИмеТипЗадължителноКакво представлява
idUuidДаOurs, and also the provisioning workflow's id and the machine's name at the provider — which is what makes the whole purchase path idempotent.
namestringДаWhat the customer called it. ⛔ At the provider a machine's name is its row id; confusing the two is a cross-tenant defect, so this is the customer's string and nothing else.
deploy_targetstringДаWhich compute range the machine belongs to.
plan_codestringДаThe tier it was bought on, or "" when it was ordered by size alone.
providerstringДаOur provider id.
specstringДаThe machine size it currently runs.
zonestringДаThe data centre it runs in.
statusstring<pending, provisioning, active, failed, suspended, terminated, resizing, terminating>ДаHow far the order got — ours, and a different fact from power_state. pending is a row with nothing bought and nothing charged; failed is the state whose message is the…
messagestringДаWhy the order failed, in a sentence the customer reads. Blank unless failed.
vendor_statusstringДаThe provider's own word, verbatim and unrounded. Staff-facing detail; a customer client renders status and never this.
power_statestring<unknown, on, off, starting, stopping, rebooting>ДаWhat the machine is doing right now. ⛔ Six values, not two, and the four extra ones are the point: a machine mid-transition is not "on". unknown is the honest answer when…
addressesstring[]ДаPublic addresses if the provider states them. Empty means not stated, never "none" — a machine rendered as having no address reads as broken.
optimisationstringДаThe stack optimisation profile it was built with, or "" for none.
term_monthsintegerДаThe term it was bought on, or null when the provider states none.
renews_atstringДаAlways null today, and honestly so: the provider publishes no renewal date, and one computed from the order plus the term would be our arithmetic rendered as the provider's…
created_atstringДаWhen the row was created, or "" when not stated.
operablebooleanДаWhether the customer may act on this machine — power, resize, renew, rebuild. ⛔ Read rather than re-derived from status: the engine refuses every one of those on anything but…
imagestringДаThe provider image the machine was built from. Blank on the resold range, which installs one managed image and offers no choice.
suspendedbooleanДа⛔⛔ Whether WE stopped it, which is not the same fact as power_state. A stopped machine is the customer's own choice and they may start it again; a suspended one is ours and…
suspension_reasonstringДаWhy, verbatim, so the customer reads the same sentence support wrote. Blank when the machine is in good standing.
capabilitiesstring[]Да⭐⭐ What this machine's provider can actually do — capability tokens such as compute:snapshots, compute:console, compute:firewall, compute:backups_manage and…
billingComputeServerBillingДаHow a machine is paid for (W43-47, docs/687). term machines are charged ahead by a per-machine subscription. metered machines are charged per started hour from the account…
login_userstringДаThe account to sign in as (W43-49, docs/689). admin — key-only, passwordless sudo, root login refused — on a Zinn® Cloud machine built under the access model; root on one…
blueprintstring<, docker, k3s, k3s_argocd>ДаThe software stack installed at first boot. Blank for none.
cluster_idstringДаThe cluster this machine is a node of, or blank.
cluster_rolestring<, server, agent>Да

Грешки, които този крайpoint може да върне

401 · 403 · 404 · 422 · 429 · 503