Deploy Workflow

This page explains the lifecycle you see when running enclavely deploy.

The deploy pipeline

1. Validate deploy input

The CLI validates required flags and optional digests. If you omit digest flags, Enclavely assigns managed digest metadata automatically.

2. Create the release

Enclavely creates an immutable release record tied to the provided project/environment and digests.

3. Queue execution

The release moves to queued, then to running when execution starts.

4. Run readiness + health checks

Enclavely validates deploy prerequisites and service health before marking the release healthy.

5. Update routing

When a release is healthy, routing is updated to target that release for the environment.

Preflight checks

enclavely readiness --project payments-service

Example: full deploy command

enclavely deploy \
  --project payments-service \
  --env qa \
  --wait \
  --timeout-sec 300

This deploys to the selected environment and waits up to 5 minutes for a terminal status.

Handling failures

If any step in the pipeline fails, the release is marked failed and no traffic is routed to it. You can inspect the failure from the CLI or dashboard:

# View the failed release
enclavely release get --project payments-service --latest --env qa

# Retry the latest failed release in an environment
enclavely release retry --project payments-service --latest-failed --env qa

Next steps

• Command Reference -- flags and options for every CLI command
• Releases -- inspect states, retry, and rollback
• Quick Start -- install the CLI and deploy your first enclave