Ryan Oaks

I've confirmed this is still an issue. Import is effectively broken for this resource, in that it requires a subsequent recreation to resolve (or hand-editing the state). Recommendation is to:...

Note: I changed this to be a deprecation instead of a removal just to be safe

@zli82016 no problem, I created https://github.com/hashicorp/terraform-provider-google/issues/21516. Let me know if there are any other labels it needs.

Heads up that https://github.com/GoogleCloudPlatform/magic-modules/pull/10817 is extremely related. I would ask that you please make every attempt to test this implementation locally, as I'm asking the other contributor to do, to...

@BBBmau Just to follow up on the above, I was able to follow up with this contributor over chat, and they were able to get their local setup working up...

Adding review label until we determine an appropriate type that can be forwarded

This is how I'm understanding the current state: - The key value of the signed URL key is expected to use https://tools.ietf.org/html/rfc4648#section-5. This is reflected in the [Terraform docs](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_backend_bucket_signed_url_key.html#key_value) and...

Forwarding to the service team to weigh in. I think we've determined the gcloud surface does not accept a Base64 URL without `=` padding, while the Terraform surface does. Would...

Thanks @pawelJas ! I'm going to keep this issue open until that time just so we can confirm the full flow works as intended.

Confirmed that this is now resolved after updating gcloud.