3 ms·
The major benefit of CF (if you don't need to manage non-AWS resources) are rollbacks. Basically, in almost all situations, if something cannot be provisioned,
by watermelon0 5y ago
The major benefit of CF (if you don't need to manage non-AWS resources) are rollbacks. Basically, in almost all situations, if something cannot be provisioned, or a service doesn't become healthy, CF would roll back to the previous state.
With Terraform you are mostly on your own, and you can easily end up in broken state, which needs to be manually fixed.
- Dobbs 5y ago> Basically, in almost all situations, if something cannot be provisioned, or a service doesn't become healthy, CF would roll back to the previous state. Until it doesn't and then you are in a completely unfixable state, must file support tickets and get AWS support to debug it and figure out how to unbork it. Meanwhile terraform gives you tools to investigate and fix it.
- mixedCase 5y agoUnless I was doing something really stupid with null_resources, a rollback for me has always been achievable either over a terraform destroy, or a new terraform apply after reverting a commit.