-
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
[Terraform]: Make google_storage_default_object_acl authoritative. #628
[Terraform]: Make google_storage_default_object_acl authoritative. #628
Conversation
} | ||
} else { | ||
res.DefaultObjectAcl = defaultObjectAcl | ||
_, err = config.clientStorage.Buckets.Update(bucket, res).Do() |
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.
Tiny race condition perhaps? If changes are made the the bucket itself during this update then would this override them?
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.
You're right! Looks like we can use metadatageneration to stop it - fixed.
I am a robot that works on MagicModules PRs! I built this PR into one or more PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
I am (still) a robot that works on MagicModules PRs! I just wanted to let you know that your changes (as of commit 63a3ff0) have been included in your existing downstream PRs. |
Tracked submodules are build/terraform-beta build/terraform build/ansible build/inspec.
Part of hashicorp/terraform-provider-google#1167
Originally was gonna look a lot more like #606 but it turns out it doesn't need to (and #606 can likely be simplified too w/o a breaking change)
[all]
[terraform]
Make google_storage_default_object_acl authoritative.
[terraform-beta]
[ansible]
[inspec]