google_storage_bucket_acl tries to delete owner access

[selmanj]

Not clear why this is happening yet, but it appears that when trying to manage acls with field role_entity on resource google_storage_bucket_acl, they are applied one at a time and accidentally attempting to remove owners access, causing an error.

Terraform Version

Terraform v0.10.0-dev (be900e808506efb018bd6adbe457cfcbaf6281a9)
(master of terraform-provider-google)

Affected Resource(s)

• google_storage_bucket_acl

Terraform Configuration Files

resource "google_storage_bucket" "log-bucket" {
    name     = "my-unique-bucket"
}

resource "google_storage_bucket_acl" "log-bucket-acl" {
  bucket = "${google_storage_bucket.log-bucket.name}"

  role_entity = [
    "OWNER:project-owners-943217423282",
    "OWNER:project-editors-943217423282",
    "READER:project-viewers-943217423282",
    "OWNER:[email protected]"
  ]
}

Expected Behavior

Should have applied acl list.

Actual Behavior

Received this error:

Error applying plan:

1 error(s) occurred:

* google_storage_bucket_acl.log-bucket-acl: 1 error(s) occurred:

* google_storage_bucket_acl.log-bucket-acl: Error updating ACL for bucket my-unique-bucket: googleapi: Error 403: The owner of the resource is required to have OWNER access., forbidden

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Steps to Reproduce

1. terraform apply

[paddycarver]

This should be addressed by #439.

[selmanj]

👍

[ghost]

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!