We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We've recently started to observe the following failures happening every few days:
00:03:30.524 dyn_record.CNAME_fancy: Refreshing state... [id=123445993] 00:03:30.782 dyn_record.CNAME_boring: Refreshing state... [id=123445232] 00:03:32.158 ╷ 00:03:32.158 │ Error: Couldn't find Dyn record: too many requests
Not sure if it's only us.
I wonder if there's any retry/sleep which could help on the Terraform side of things (other than asking Dyn to change their rate limiting).
The text was updated successfully, but these errors were encountered:
We don't have that many records:
# grep -r "resource \"dyn" . | wc -l 377
I am not sure what is the scope of the rate-limiting on Dyn side - i.e. is the time bucket per second or per day, etc.
Sorry, something went wrong.
Their docs say:
The default rate limit is currently 300 requests per minute, or 5 requests per second
No branches or pull requests
We've recently started to observe the following failures happening every few days:
Not sure if it's only us.
I wonder if there's any retry/sleep which could help on the Terraform side of things (other than asking Dyn to change their rate limiting).
The text was updated successfully, but these errors were encountered: