compute

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

Reinstall a server's operating system.

Ҳамаи нуқтаҳои ниҳоии compute

Ҳамаи ҳуҷҷатҳои таҳиякунандагон

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати sites.view бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

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> }'

Воarid шудаед? Консоли 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.

Параметрҳо

НомНамудТалаб карда мешавадИн чӣ аст
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>Бале

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 422 · 429 · 503