cb5062d237
We create hundreds of AWS Elasticsearch resources over the last few months and we get occasional timeout failures from AWS. This will PR is to increase the timeout once again. I did it before: https://github.com/hashicorp/terraform/pull/5910/files But we've seen enough timeouts from AWS on this resource that increasing the timeout seems like the only solution. |
||
|---|---|---|
| .. | ||
| atlas | ||
| aws | ||
| azure | ||
| azurerm | ||
| chef | ||
| clc | ||
| cloudflare | ||
| cloudstack | ||
| cobbler | ||
| consul | ||
| datadog | ||
| digitalocean | ||
| dme | ||
| dnsimple | ||
| docker | ||
| dyn | ||
| fastly | ||
| github | ||
| grafana | ||
| heroku | ||
| influxdb | ||
| librato | ||
| logentries | ||
| mailgun | ||
| mysql | ||
| null | ||
| openstack | ||
| packet | ||
| postgresql | ||
| powerdns | ||
| random | ||
| rundeck | ||
| scaleway | ||
| softlayer | ||
| statuscake | ||
| template | ||
| terraform | ||
| test | ||
| tls | ||
| triton | ||
| ultradns | ||
| vcd | ||
| vsphere | ||