Does ControlTier support undeploy/rollback?
The simple answer is that you want to “roll forward” to a previously known good release. In actual practice it is not always so simple. There are two strategies for managing undeploy or rollback using ControlTier: model-driven vs. module-driven. • Model-driven reversion is based on completely model-driven commands and ControlTier’s versioned model. By rolling the model back to a previous state, and re-running the deployment, you effectively bring the deployment back to the previous configuration state. The model-driven strategy is the favored approach as it assumes the state of the configuration model has the primary affect over the behavior of commands. In essence, this just means ControlTier encourages a data-driven programming style. • Module-driven reversion relies on rollback logic that is contained in the control module and may or may not be driven from the centrally managed model state. Module-driven reversion is typically only used for custom applications or databases who’s int
