Hacker News new | ask | show | jobs
by nikolay 1909 days ago
For a person who uses Terraform daily, I won't agree with you. So many times I had to manually alter state files, and often contribute to basic providers, and wait months to get PRs merged in. It used to be that CloudFormation lagged behind Terraform for AWS, but not anymore. Now, it's quite the opposite and you see people using CloudFormation resource within Terraform as they are stuck into using plain Terraform and yet don't want to manage resource manually.
1 comments

You won’t find argument from me that HashiCorp have let maintenance slide, but there is still no conceivable way that CFN is more reliable in the general case.
Hmmm, just searched GitHub for aws_cloudformation_stack and found 375 public repositories. I'm sure those references are orders of magnitude more in the private repos. In other words, you still need CloudFormation with Terraform on AWS... so, why use the patchwork then?