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

GCS: diable uniform_bucket_level_access #4

Merged
merged 1 commit into from
Apr 13, 2024

Conversation

Shion1305
Copy link
Member

No description provided.

Copy link

Plan Result (dev)

CI link

Plan: 1 to add, 1 to change, 0 to destroy.
  • Create
    • google_storage_bucket_access_control.public_image_bucket
  • Update
    • google_storage_bucket.public_image_bucket
Change Result (Click me)
  # google_storage_bucket.public_image_bucket will be updated in-place
  ~ resource "google_storage_bucket" "public_image_bucket" {
        id                          = "lgtm-public-image-bucket"
        name                        = "lgtm-public-image-bucket"
      ~ uniform_bucket_level_access = true -> false
        # (13 unchanged attributes hidden)

      ~ cors {
          ~ origin          = [
              + null,
            ]
            # (3 unchanged attributes hidden)
        }
    }

  # google_storage_bucket_access_control.public_image_bucket will be created
  + resource "google_storage_bucket_access_control" "public_image_bucket" {
      + bucket = "lgtm-public-image-bucket"
      + domain = (known after apply)
      + email  = (known after apply)
      + entity = "allUsers"
      + id     = (known after apply)
      + role   = "READER"
    }

Plan: 1 to add, 1 to change, 0 to destroy.

@Shion1305 Shion1305 merged commit fcef837 into main Apr 13, 2024
1 check passed
@Shion1305 Shion1305 deleted the fix-gcs-public-image-unform-access branch April 13, 2024 03:15
Copy link

✅ Apply Succeeded (dev)

CI link

Apply complete! Resources: 1 added, 1 changed, 0 destroyed.
Details (Click me)
google_storage_bucket.public_image_bucket: Refreshing state... [id=lgtm-public-image-bucket]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create
  ~ update in-place

Terraform will perform the following actions:

  # google_storage_bucket.public_image_bucket will be updated in-place
  ~ resource "google_storage_bucket" "public_image_bucket" {
        id                          = "lgtm-public-image-bucket"
        name                        = "lgtm-public-image-bucket"
      ~ uniform_bucket_level_access = true -> false
        # (13 unchanged attributes hidden)

      ~ cors {
          ~ origin          = [
              + null,
            ]
            # (3 unchanged attributes hidden)
        }
    }

  # google_storage_bucket_access_control.public_image_bucket will be created
  + resource "google_storage_bucket_access_control" "public_image_bucket" {
      + bucket = "lgtm-public-image-bucket"
      + domain = (known after apply)
      + email  = (known after apply)
      + entity = "allUsers"
      + id     = (known after apply)
      + role   = "READER"
    }

Plan: 1 to add, 1 to change, 0 to destroy.
google_storage_bucket.public_image_bucket: Modifying... [id=lgtm-public-image-bucket]
google_storage_bucket.public_image_bucket: Modifications complete after 1s [id=lgtm-public-image-bucket]
google_storage_bucket_access_control.public_image_bucket: Creating...
google_storage_bucket_access_control.public_image_bucket: Creation complete after 1s [id=lgtm-public-image-bucket/allUsers]
Releasing state lock. This may take a few moments...

Apply complete! Resources: 1 added, 1 changed, 0 destroyed.

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.

1 participant