Trigger deployment
| Parameter | Type | Required | Description |
|---|---|---|---|
productionAppId | body | Yes | Production app to deploy to |
versionId | body | No | Specific version to deploy (defaults to active version) |
entities:deploy scope + entity publisher.
List deployments
| Parameter | Type | Description |
|---|---|---|
productionAppId | query | Filter by production app |
status | query | Filter by deployment status |
page | query | Page number (default: 1) |
pageSize | query | Items per page (default: 20) |
Get deployment
Cancel deployment
entities:deploy scope + entity publisher.
Deployment phases
Each deployment progresses through the following phases:| Phase | Description |
|---|---|
orchestrate | Initial deployment orchestration |
download | Download entity package |
infra | Provision or update infrastructure |
build | Build the application |
package | Package for deployment |
migrate | Run database migrations |
service_deploy | Deploy to compute infrastructure |
cache_invalidation | Invalidate CDN caches |
pending, in_progress, completed, or failed. The platform streams real-time logs for each phase as the deployment progresses.
Deployment lifecycle
pending, moves to in_progress when the pipeline begins processing, and ends as completed, failed, or cancelled.
Failed deployments include an error message. Cancelled deployments stop the pipeline at the current phase.
