Deployment Configuration
The Deploy stage defines where and how your application is deployed. Click on the Deploy node in the workflow builder to open the configuration panel.
Environment Selection
Select one or more target environments for deployment. Each environment is deployed sequentially in the order listed.
| Field | Description |
|---|---|
| Environment | Select an active environment where the service will be deployed. You can add multiple environments. |
Only active environments are available for selection. If your target environment is stopped or destroyed, start or recreate it before configuring the deployment.
Multi-Environment Deployment
You can deploy to multiple environments within a single workflow — for example, Dev → Staging → Production. Each environment is configured independently with its own deployment type and approvers.
Environments are deployed sequentially in the order they appear in the configuration. The next environment only begins deployment after the previous one completes successfully (or receives approval if manual).
Deployment Type
For each environment, choose how the deployment is triggered:
| Type | Description |
|---|---|
| Automatic | Deployment occurs automatically upon successful completion of the preceding stage (Build/Push or previous environment's deployment). |
| Manual | Deployment waits in Deployment Pending status until a user manually triggers it or until designated approvers approve the deployment. |
Approval Workflow
When the deployment type is Manual, you can optionally configure an approval gate:
| Field | Description |
|---|---|
| Enable Approvers | Toggle to require approval before the deployment proceeds. |
| Approvers | Select one or more users who are authorized to approve or reject the deployment. |
How Approval Works
- When the pipeline reaches a manual environment with approvers enabled, the status changes to Approval Pending.
- Designated approvers receive a notification (email and in-app).
- An approver can Approve or Reject the deployment, optionally adding a comment.
- If approved, the deployment proceeds automatically.
- If rejected, the deployment is cancelled and the status changes to Approval Rejected.
To configure approvers, your role must have the Add approver to workflows permission. To approve or reject deployments, your role must have the Approve pipeline permission.
Deployment Flow Example
A typical multi-environment workflow with approval gates:
| Environment | Deployment Type | Approvers | Behavior |
|---|---|---|---|
| Development | Automatic | None | Deploys automatically after the Push stage completes. |
| Staging | Automatic | None | Deploys automatically after Development deployment succeeds. |
| Production | Manual | Team Lead, DevOps Lead | Waits for approval. Once approved, deploys to production. |
Saving the Configuration
Click Save at the bottom of the panel to apply your deployment configuration.