Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:d:deployment_rollback [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:d:deployment_rollback [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Deployment Rollback ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Deployment Rollback is a [[public: | ||
| + | |||
| + | A Deployment Rollback may apply to: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Relationships among deployed subjects | ||
| + | * A resulting [[public: | ||
| + | |||
| + | The predeployment state may be identified through: | ||
| + | |||
| + | * A deployment record | ||
| + | * A prior [[public: | ||
| + | * A prior [[public: | ||
| + | * A prior [[public: | ||
| + | * A prior [[public: | ||
| + | * 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 ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== 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 [[public: | ||
| + | |||
| + | 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. | ||
| + | </ | ||