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

Uniform access control for storage bucket #5875

Closed
elsbrock opened this issue Mar 10, 2020 · 3 comments · Fixed by GoogleCloudPlatform/magic-modules#3916, #7143 or hashicorp/terraform-provider-google-beta#2442

Comments

@elsbrock
Copy link

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

Google Cloud Security Command Center recommends using storage buckets with uniform access control. I am unable to find information about this in the provider docs, so I assume this is currently not supported.

New or Affected Resource(s)

  • google_storage_bucket

References

see https://cloud.google.com/storage/docs/uniform-bucket-level-access

@ghost ghost added the enhancement label Mar 10, 2020
@danawillow
Copy link
Contributor

Hey @elsbrock, we do support this via the bucket_policy_only field, which unfortunately was renamed at a product level after we had already added support, which is why it wasn't immediately obvious that it's the same thing. I'm going to relabel this as a documentation issue, because we can definitely do a better job at clarifying what that field is.

@elsbrock
Copy link
Author

Perfect, thank you!

@ghost
Copy link

ghost commented Sep 28, 2020

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Sep 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.