-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
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
Add retries/backoff when (only) reading IAM policies #1665
Add retries/backoff when (only) reading IAM policies #1665
Conversation
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesNo diff detected in terraform-google-conversion. New Pull RequestsI built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
This seems similar to https://github.com/GoogleCloudPlatform/magic-modules/pull/1609/files; what do you think about using https://github.com/terraform-providers/terraform-provider-google/blob/master/google/utils.go#L337 or similar instead? Our API technically prefers exponential backoff, but standardising our retry logic feels worth not listening. |
@rileykarson Originally I wasn't sure if this was related to an issue with retryTime but it eventually morphed into something that was retryTime. I'll change it. |
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Not sure if the test is necessary now that we're using a standard retry fn
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
Tracked submodules are build/terraform-beta build/terraform-mapper build/terraform build/ansible build/inspec.
We currently do a lot of retry logic around modifying IAM policies, but most resources call the IAM policy read command without retry/backoff logic. This is (potentially) leading to issues like b/130308440 where multiple members being added at the same time is hitting quotas during just the read.
[all]
[terraform]
Add retries/backoff when (only) reading IAM policies
[terraform-beta]
Add retries/backoff when (only) reading IAM policies
[ansible]
[inspec]