Open dan-mcdonald opened 1 year ago
I'm getting this issue intermittently, did you find a workaround ? @dan-mcdonald
We do have the same problem and it appears quite often on our plan
execution, which is very problematic for us. I'm surprised to read from the API documentation^1:
Rate limit
Gandi's API is rate limited; you can perform a maximum of 1000 requests per minute from the same IP address.
which we are definitively not hitting.
Moreover, looking at the code / reference there is a (strange) custom default key to configure the timeout for the nemserver records: https://registry.terraform.io/providers/go-gandi/gandi/latest/docs/resources/nameservers#default
Adding this block in the resource did not even fix the problem:
resource "gandi_nameservers" "example" {
...
timeouts {
default = 60
}
}
[!NOTE] The provider code has some code for a default timeout, which is not exposed in the provider configuration, with a default value of 5 seconds.
:shrug:
I'm running into this essentially every time I run terraform plan
, which is very frustrating.
It seems like the plugin passes config back to the go-gandi
library here:
The library exposes a timeout
option (defaulting to 5 seconds) which the terraform provider doesn't provide a way to override:
Ideally Gandi would fix their API so it wasn't so slow, but as an interim solution it'd be nice to be able to override the timeout config
We solved it the hard way... moving away from Gandi.
I'm trying to add a new
A
record to my Gandi LiveDNS with this provider.But during apply I get this error (run with TF_LOG=INFO):
I think the request will work if it is given more time. My internet connection is not the fastest. Is there a configuration knob to increase the timeout? Currently it fails for me after only 10/15 seconds.
Other details:
Any help you provide is appreciated. I know I'm not entitled to any free help.