4 ms·
It's not fair to compare imperative simple shell scripts with the things Terraform does. It has schema validation, state comparison, retries, failure handlers e
by CSDude 5y ago
It's not fair to compare imperative simple shell scripts with the things Terraform does. It has schema validation, state comparison, retries, failure handlers etc.
Also, just as you can write extensions to kubectl, you can write your own provider in Terraform if it does not exists. See https://registry.terraform.io/modules/waveaccounting/chatbot-slack-configuration/aws/latest https://registry.terraform.io/modules/waveaccounting/chatbot...
Also, Chatbot does not have a public API, that's why, it's only configured via Cloudformation. So the expectation is not fair either.
I've seen Cloudformation getting features years later. i.e
2021 - https://aws.amazon.com/about-aws/whats-new/2021/05/amazon-dynamodb-global-tables-now-support-aws-cloudformation/ https://aws.amazon.com/about-aws/whats-new/2021/05/amazon-dy...
2015 - https://aws.amazon.com/about-aws/whats-new/2015/07/amazon-dynamodb-available-now-cross-region-replication-triggers-and-streams/ https://aws.amazon.com/about-aws/whats-new/2015/07/amazon-dy...
- jen20 5y agoNAT Gateways is another notable feature that took CloudFormation months yet Terraform had on day 1. If you can configure something via CloudFormation you can integrate it via Terraform et al also, since they have resources representing CloudFormation stacks.
- lincler 5y agoThis! Is not like you can't go beyond what Terraform offers by default. Running CloudFormation stacks from Terraform is a neat way of solving missing apis/integration. And that's exactly what my team did when Terraform was missing a lot of lambdas functionalities. We just declared the CloudFormation Stack for lambdas and then call it from Terraform.