3 ms·
You're absolutely right. I started using Terraform around 2016 and it was pretty common to get barked at by the AWS API if you were repeatedly running plans, ev
by ericbarrett 4y ago
You're absolutely right. I started using Terraform around 2016 and it was pretty common to get barked at by the AWS API if you were repeatedly running plans, even with state. I bet the cloud providers have had to make significant infra changes to support the growing number of customers using TF.
- scarface74 4y agoThere are still plenty of services in AWS that have painfully low service limits for API calls. The first one that bit me was creating parameters in SSM Parameter Store using CloudFormation. CF tries to create as many resources in parallel as possible based on the dependency graph it creates. The only way around it was making each Parameter resource dependent on the other (using DependsOn) to force the resources to be created sequentially. Before the CF vs TF holy wars began, this is an API limitation that you would hit regardless of your IAC.