terraform-provider-google: google provider is rejected from gcp API for frequent request
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the “modular-magician” user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to “hashibot”, a community member has claimed the issue already.
Description
When I was applying google provider to GCP, terraform plan failed with API timeout.
Error: Error reading Container NodePool xxx: Get https://container.googleapis.com/v1beta1/projects/xxx/locations/us-central1/clusters/xxx/nodePools/xxx?alt=json&prettyPrint=false: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Finally I found that I have to reduce parallelism of terraform.
$ terraform plan --parallelism=1
If it’s possible I want google-provider to handle parallelism by itself.
Version
Terraform v0.12.24
- provider.google v3.15.0
- provider.google-beta v3.15.0
New or Affected Resource(s)
- google_XXXXX
Potential Terraform Configuration
# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.
References
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 18 (8 by maintainers)
Thank you, those are super helpful! I have some changes I’d like to make that should improve this (it might not fix it 100% but should make it better in some cases). Will keep you informed.