compute

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

Move a server onto another machine size.

تمام compute اینڈ پوائنٹس

تمام ڈویلپر دستاویزات

توثيقِ شناخت

ایک بیرر ٹوکن کے طور پر ایک API کی بھیجیں۔ کی کے پاس sites.view اجازت ہونی چاہیے؛ اس کے بغیر کی کو 404 کے بجائے 403 کے ساتھ مسترد کر دیا جاتا ہے۔

یہ اینڈ پوائنٹ کوئی آرگنائزیشن آئی ڈی نہیں لیتا۔ آپ کی کلید پہلے ہی اس آرگنائزیشن کی شناخت کرتی ہے جس سے یہ تعلق رکھتی ہے، اور اس کا جواب اسی کے مطابق محدود ہوتا ہے۔

آزمائیں

کوئی بھی چیز جو زاویہ دار قوسین میں ہو اسے اپنی اقدار سے بدلیں، اور کلیدی پلیس ہولڈر کو اپنے ڈیش بورڈ کی کسی کلید سے بدلیں۔

curl -X POST https://api.zinndigital.com/v1/compute/servers/{serverId}/resize \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

لاگ ان ہیں؟ آپ کے ڈیش بورڈ میں موجود API کنسول آپ کی حقیقی تنظیم کی آئی ڈی اور آپ کی اپنی کلید خود بخود پُر کر دیتا ہے، اور لائیو API پر درخواست چلاتا ہے تاکہ آپ اصل ردعمل دیکھ سکیں۔ اس اینڈ پوائنٹ کو API کنسول میں کھولیں

تفصیلات

Performs the upgrade and returns the server's new state. ⛔ This charges immediately at every provider we support, so it is only ever reached from a quote the customer has read (quoteComputeServerResize). The engine attaches an idempotency key derived from the server and the target size, so a retry cannot buy the resize twice. ⛔⛔ A size whose disk is smaller than what the machine is already using is refused with a 422, and that is a data-loss gate rather than a tidiness check. The provider's endpoint is an upgrade endpoint and usually refuses a shrink, but "usually" is not a promise to make about a customer's files. Before a shrink the engine reads the machine's live disk usage and requires the target to be strictly larger. It fails closed: if the provider does not answer, or answers -1 ("did not say"), the resize is refused rather than attempted — -1 < anything would otherwise read as "plenty of room". Growing is never gated, never pays for the extra read, and never fails because usage statistics were unavailable. RAM is not gated: running with less memory loses nothing on disk and is the customer's call. 404 for a server that is not the caller's; 422 for a size the provider does not offer, a machine that is not active — an order still running would have two writers, and a failed or released one has nothing to write to — or a shrink below the disk in use. Requires sites.view and billing.payment.manage — ⛔ not sites.create, which is what this was until #1682.

پیرامیٹرز

نامقسملازمییہ کیا ہے
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.

درخواست کا باڈی

نامقسملازمییہ کیا ہے
specstringنہیںThe target size, as getComputeCatalogue reported it.
plan_codestringنہیںThe plan to move to, as getComputeCatalogue's tiers[].plan_code.

جواب

نامقسملازمییہ کیا ہے
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…

وہ خرابیان جو یہ اینڈ پوائنٹ واپس کر سکتا ہے

401 · 403 · 404 · 422 · 429 · 503