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

provider/google/storage: support for defaultObjectAccessControls #64

Closed
hashibot opened this issue Jun 13, 2017 · 2 comments
Closed

provider/google/storage: support for defaultObjectAccessControls #64

hashibot opened this issue Jun 13, 2017 · 2 comments

Comments

@hashibot
Copy link

This issue was originally opened by @renchap as hashicorp/terraform#12481. It was migrated here as part of the provider split. The original body of the issue is below.


In the same way as google_storage_bucket_acl and google_storage_object_acl there should be a google_storage_default_object_acl to be able to specify the default ACL for new objects in a bucket. This is useful for example in a public bucket where you want all objects to be readable by anybody.

API documentation here : https://cloud.google.com/storage/docs/json_api/v1/defaultObjectAccessControls

Example:

resource "google_storage_default_object_acl" "public-read-acl" {
  bucket = "${google_storage_bucket.bucket.name}"
  role_entity = [
    "OWNER:project-owners-123456",
    "READER:allUsers"
  ]
}
@danawillow
Copy link
Contributor

Fixed in #992

luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
Remove files that aren't managed by magic-modules or explicitly excluded.
@ghost
Copy link

ghost commented Mar 29, 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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants