terraform-provider-vultr: rate_limit does not seem to be limiting the request rate to Vultr properly preventing the use of -parallelism=24

Vultr has a horribly slow request rate limit at 2/sec. So when using this provider driver combined with other providers or have a node count higher than 2-3 it generates rate limit errors even on terraform plan. You have to end up using terraform plan -parallelism=3 so it even works slowing down your overall deployment considerably. The only workaround I have found is to add a provisioner for a local 10 minute sleep after each vultr server deploy and separately creating a plan file first. However, this is unreliable. provisioner "local-exec" { command = "sleep 600" }

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 20 (6 by maintainers)

Most upvoted comments

@Obsecurus

We are going to update terraform and run through make sure everything is working properly and then cut a release shortly thereafter

I will keep this open and use this to address any PRs ill make.

As for issues:

  • The rate_limit in your case not being properly applied. Although if I set my rate_limit to 10000 it does wait 10 seconds in between calls. I will still dig into this one for you though.

  • The retry to govultr is an enhancement which will improve user experience