Deployment States

A deployment can move between different states throughout its lifetime. If you make a request to change a deployment, the deployment state will change based on the nature of your request and whether the request was successful.

A deployment state is the current status of the deployment. For example, a successful deployment can have a state of DEPLOYED and a failed deployment might have a state of DEPLOYMENT_FAILED.

Before you begin

Possible states

Deployments can have the following states:

  • DEPLOYED—The deployment was successfully deployed from a previous request.
  • PREVIEWING—The deployment is being previewed; no resources have yet been created from this preview request.
  • DEPLOYMENT_FAILED—The deployment was not successfully created or updated, or you stopped an in-progress update to the deployment. If an in-progress update was stopped, then there will be no errors. If the deployment failed on its own, you can view any errors in the deployments.update.errors property. If the error was caused by a specific resource, the resource will have an resource.update.state of FAILED. View the resource error in the resources.update.errors property.
  • UPDATING—The deployment is being updated.

Actions that change states

The following actions will change the deployment state:

Progression of state changes

Some state changes are not allowed, while other states can change to a number of available states. Use this diagram to understand the possible state changes for your deployment.

For example, a deployment with a DEPLOYMENT_FAILED state can move to a UPDATING or PREVIEWING state but cannot move directly to a DEPLOYED state.

Diagram for deployment state changes (click to enlarge)
Diagram for deployment state changes (click to enlarge)
Was this page helpful? Let us know how we did:

Send feedback about...

Cloud Deployment Manager Documentation