5 ms·
I absolutely can't stand how destructive terraform is by nature. We have switched to Ansible, which has an excellent AWS module, and never looked back.
by johnmarcus 9y ago
I absolutely can't stand how destructive terraform is by nature. We have switched to Ansible, which has an excellent AWS module, and never looked back.
- smt88 9y agoWhy Ansible rather than Elastic Beanstalk or Cloud Formation?
- an27 9y agoIt's vendor-agnostic? And CF is super slow and limited to a small number of resources (not sure if it's a 100 or a 1000).
- paulddraper 9y agoDefinitely 100. And every little thing is a resource.
- 80x25 9y agohttp://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuid... Am I a missing something? Nothing in these docs about a 100 resource limit
- paulddraper 9y agoIt used to be 100. Looks like it's 200 now.
- 80x25 9y agoThat's 200 resources per CF template. That's a massive CF template :)
- tjbiddle 9y agoWhat do you mean by destructive by nature? A resource will only be destroyed if: 1) You remove it explicitly from your configuration; which should be the intended result - it's no longer a "part of your infrastructure" 2) You've change some attribute that requires your provider to replace the instance entirely - Trying to think of an example off hand... While not applicable anymore as AWS now supports applying/changing IAM roles to running instances now, had you done something like that in the past, that would've forced a resource replacement.