Sign in

v37

latestOpenAPI 3.1.0raw.githubusercontent.com2025-11-11200148.2 KB
Stacks

Apply partial update to stack

Update stack files using manifest + bundle format and/or individual operations. For multi-service stacks, changes are routed to appropriate services.

post/v1/stacks/{id}/patch

Path parameters

idstring required

Stack identifier

Example:stk_abc123

Headers

base-etagstring

Current stack etag for conflict detection

Example:sha256:abc123...
idempotency-keystring required

Unique key for idempotent requests

Example:key-12345678

Response

Patch applied successfully

idstring required

Stack identifier

phase'starting' | 'building' | 'deploying' | 'running' | 'failed' | 'stopped' required

Stack lifecycle phases

appliednumber required

Number of operations applied

etagstring required

New ETag after changes

restartedboolean required

Whether stack was restarted

warningsstring[]

Optional warnings if patch partially failed

affectedServicesstring[]

Services affected by patch (for multi-service stacks)

Example response

{
  "id": "stk_abc123",
  "phase": "running",
  "applied": 5,
  "etag": "sha256:new123...",
  "restarted": true,
  "warnings": [
    "File not found: old-file.js"
  ],
  "affectedServices": [
    "web",
    "api"
  ]
}