Skip to content
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

Merged
merged 5 commits into from
Apr 19, 2019

Conversation

emilymye
Copy link
Contributor

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]

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician, I work on Magic Modules.
This PR seems not to have generated downstream PRs before, as of 24037f9.

Pull request statuses

No diff detected in terraform-google-conversion.
No diff detected in Ansible.
No diff detected in Inspec.

New Pull Requests

I 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.
depends: hashicorp/terraform-provider-google-beta#620
depends: hashicorp/terraform-provider-google#3455

@rileykarson
Copy link
Member

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.

@emilymye
Copy link
Contributor Author

@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.

@emilymye emilymye removed the request for review from chrisst April 18, 2019 20:45
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician, I work on Magic Modules.
I see that this PR has already had some downstream PRs generated. Any open downstreams are already updated to your most recent commit, f1bf52b.

Pull request statuses

terraform-provider-google-beta already has an open PR.
No diff detected in terraform-google-conversion.
terraform-provider-google already has an open PR.
No diff detected in Ansible.
No diff detected in Inspec.

New Pull Requests

I didn't open any new pull requests because of this PR.

Copy link
Member

@rileykarson rileykarson left a 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

third_party/terraform/utils/iam.go Outdated Show resolved Hide resolved
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician, I work on Magic Modules.
I see that this PR has already had some downstream PRs generated. Any open downstreams are already updated to your most recent commit, 08c04b8.

Pull request statuses

terraform-provider-google-beta already has an open PR.
No diff detected in terraform-google-conversion.
terraform-provider-google already has an open PR.
No diff detected in Ansible.
No diff detected in Inspec.

New Pull Requests

I 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.
@modular-magician modular-magician merged commit e74a54c into GoogleCloudPlatform:master Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants