Takomo 11.1.0 adds support for the new CloudFormation express mode, as well as disabling stack rollback, through a new deploymentConfig stack property.
In the standard deployment mode, CloudFormation waits until every resource is ready to serve traffic before it completes a stack operation. In express mode, CloudFormation completes the operation as soon as the resource configuration has been applied, and the resources continue becoming ready in the background. According to AWS, this can make deployments up to four times faster.
Express mode works well in development and test environments, and for stacks whose dependents don't need the resources to be fully ready right away.
Set the deployment mode in a stack group configuration file to deploy every stack under the group in express mode:
Like other stack properties, deploymentConfig can also be defined in blueprint and stack configuration files. For example, you can deploy most stacks in express mode but keep one stack in the standard mode:
The deploymentConfig property also lets you disable stack rollback. When rollback is disabled and a stack operation fails, CloudFormation leaves the resources in their failed state, so you can find out what went wrong instead of waiting for a rollback to finish first.
Takomo handles stacks left in a failed state:
CREATE_FAILED) is deleted and created again on the next deployment.UPDATE_FAILED) is updated on the next deployment, and it can also be undeployed.The mode and disableRollback properties are inherited separately. A stack can override one of them and still inherit the other from its blueprint or stack group:
Here my-stack is deployed in express mode with rollback disabled.
See the deploymentConfig documentation for all the details.