====== Deployment Rollback ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]

===== Discussion =====

Deployment Rollback is a [[dido:99_annexes:annex-b-terms-and-definitions:r:rollback|Rollback]] that reverses the effects of an identified deployment by restoring the affected deployment subject to its identified predeployment state.

A Deployment Rollback may apply to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]]
  * Relationships among deployed subjects
  * A resulting [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]]

The predeployment state may be identified through:

  * A deployment record
  * A prior [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * A prior [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revision]]
  * A prior [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]
  * A prior [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]]
  * A checkpoint
  * Another recorded valid state

Deployment Rollback differs from deployment cancellation:

  * Deployment cancellation stops a deployment before completion
  * Deployment Rollback reverses the effects already produced by a deployment

Deployment Rollback differs from deployment retry:

  * Deployment Rollback restores the predeployment state
  * Deployment retry performs the deployment operation again

Deployment Rollback may precede a corrected deployment or another recovery operation.

===== Definition =====

//[[dido:99_annexes:annex-b-terms-and-definitions:r:rollback|rollback]] that reverses the effects of an identified deployment by restoring the affected deployment subject to its identified predeployment state//

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

===== Note =====

Deployment Rollback does not imply that every deployment effect can be reversed.

Applicable requirements should identify:

  * The deployment subject
  * The deployment is being reversed
  * The predeployment state
  * The rollback initiation condition
  * The effects included in the rollback
  * Effects excluded from the rollback
  * The required rollback result
  * The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

A Deployment Rollback may require separate handling for:

  * Persistent data
  * External services
  * Credentials
  * Messages
  * Transactions
  * Provider-managed resources
  * Changes performed outside the deployment boundary

===== Example =====

A deployment replaces a Containerized Workload with an unacceptable Revision. Crucible performs Deployment Rollback by removing the new workload Revision and restoring the workload configuration and Image used immediately before the deployment.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>