compute
POST /v1/compute/servers/{serverId}/rebuild
Reinstall a server's operating system.
Аутентификация
API кілтін bearer токені ретінде жіберіңіз. Кілтте sites.view рұқсаты болуы тиіс; онсыз кілтке 404 емес, 403 қатесі қайтарылады.
Бұл соңғы нүкте ұйым идентификаторын қабылдамайды. Сіздің кілтіңіз оның қай ұйымға тиесілі екенін өзі анықтайды және жауап соған шектеледі.
Әрекет етіп көру
Бұрыштық жақшалардағы кез келген нәрсені өз мәндеріңізбен, ал кілт орналастырушысын басқару тақтасынан алынған кілтпен алмастырыңыз.
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 арқылы орындайды. Бұл соңғы нүктені 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.
Параметрлер
| Аты | Tүрі | Міндетті | Мазмұны |
|---|---|---|---|
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. |
Сұрау денесі
| Аты | Tүрі | Міндетті | Мазмұны |
|---|---|---|---|
operating_system | string | Иә | 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,… |
confirm | string | Иә | 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… |
Жауап
| Аты | Tүрі | Міндетті | Мазмұны |
|---|---|---|---|
id | Uuid | Иә | 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. |
name | string | Иә | 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_target | string | Иә | Which compute range the machine belongs to. |
plan_code | string | Иә | The tier it was bought on, or "" when it was ordered by size alone. |
provider | string | Иә | Our provider id. |
spec | string | Иә | The machine size it currently runs. |
zone | string | Иә | The data centre it runs in. |
status | string<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… |
message | string | Иә | Why the order failed, in a sentence the customer reads. Blank unless failed. |
vendor_status | string | Иә | The provider's own word, verbatim and unrounded. Staff-facing detail; a customer client renders status and never this. |
power_state | string<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… |
addresses | string[] | Иә | Public addresses if the provider states them. Empty means not stated, never "none" — a machine rendered as having no address reads as broken. |
optimisation | string | Иә | The stack optimisation profile it was built with, or "" for none. |
term_months | integer | Иә | The term it was bought on, or null when the provider states none. |
renews_at | string | Иә | ⛔ 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_at | string | Иә | When the row was created, or "" when not stated. |
operable | boolean | Иә | 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… |
image | string | Иә | The provider image the machine was built from. Blank on the resold range, which installs one managed image and offers no choice. |
suspended | boolean | Иә | ⛔⛔ 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_reason | string | Иә | Why, verbatim, so the customer reads the same sentence support wrote. Blank when the machine is in good standing. |
capabilities | string[] | Иә | ⭐⭐ What this machine's provider can actually do — capability tokens such as compute:snapshots, compute:console, compute:firewall, compute:backups_manage and… |
billing | ComputeServerBilling | Иә | 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_user | string | Иә | 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… |
blueprint | string<, docker, k3s, k3s_argocd> | Иә | The software stack installed at first boot. Blank for none. |
cluster_id | string | Иә | The cluster this machine is a node of, or blank. |
cluster_role | string<, server, agent> | Иә | — |
Бұл соңғы нүкте қайтара алатын қателер
401 · 403 · 404 · 422 · 429 · 503