You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a project has numerous services enabled, using the "google_project_service" resource causes multiple API requests during a refresh which can often go over the API limits. By using the "google_project_services" resource, this is limited to a single API call. I was only able to fix issues with my project by swapping to using the now deprecated "google_project_services". I believe this deprecation needs to be revisited.
The text was updated successfully, but these errors were encountered:
Are you using a recent version of the provider? 2.13.0 and onwards support Batching which should cause multiple google_project_service resources to send a single request. It should be on by default.
Debug logs would be a big help, if batching isn't working for some reason. If those don't work, if you've got a list of services that will hit rate limits that would also be a big help.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Nov 16, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a project has numerous services enabled, using the "google_project_service" resource causes multiple API requests during a refresh which can often go over the API limits. By using the "google_project_services" resource, this is limited to a single API call. I was only able to fix issues with my project by swapping to using the now deprecated "google_project_services". I believe this deprecation needs to be revisited.
The text was updated successfully, but these errors were encountered: