hosting
POST /v1/sites/{siteId}/deployments/{deploymentId}/redeploy
Roll back by re-publishing an earlier deploy's commit.
Autentifikatsiya
API kalitini bearer token sifatida yuboring. Kalit hosting.deploy.manage ruxsatiga ega boʻlishi shart; ruxsatsiz kalit 404 emas, balki 403 xatosi bilan rad etiladi.
Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.
Sinab ko'rish
Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/deployments/{deploymentId}/redeploy \
-H "Authorization: Bearer zdk_live_…"Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching
Tafsilotlar
Rollback is a forward deploy of the recorded commit, not a provider-side pointer move — a provider rollback promotes a deployment that provider still holds, so it silently does nothing once that has expired, behaves differently on each backend, and leaves our history naming a commit the site is not on. A deployment with no recorded commit returns `UNPROCESSABLE_ENTITY`. Requires `hosting.deploy.manage`.
Parametrlar
| Nomi | Turi | Majburiy | Nima bu |
|---|---|---|---|
siteId (path) | Uuid | Ha | Site ID (UUIDv7). |
deploymentId (path) | Uuid | Ha | Deployment ID (UUIDv7). |
Javob
| Nomi | Turi | Majburiy | Nima bu |
|---|---|---|---|
id | Uuid | Ha | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
site_id | Uuid | Ha | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
target | DeployTarget | Ha | Where the site is published from. `fleet` is our own managed fleet; the rest are managed edge hosts, deployed to from a pooled account of ours or the customer's own connected on… |
status | DeployStatus | Ha | `idle` means the site has never been deployed. It is reported, never stored — a stored idle would be a second way to say "no deployments" that could contradict the first. |
trigger | DeployTrigger | Ha | What caused the deploy. Stored because `requested_by` cannot answer it for a push — the actor there is a webhook delivery, not a person. |
repo | object | Ha | — |
branch | object | Ha | — |
commit | object | Ha | — |
commit_message | object | Ha | — |
live_url | object | Ha | — |
message | object | Ha | Why it failed, else null. Rendered to the customer verbatim. |
requested_by | string | Ha | — |
created_at | string | Ha | — |
started_at | object | Ha | — |
finished_at | object | Ha | — |
log | string | Ha | The build log, one timestamped line per step. Truncated from the FRONT when long — the end of a build log is where the failure is. |
Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar
401 · 403 · 404 · 409 · 422 · 429 · 503