Riley Karson

Note: we should work w/ the service owners to determine how to untangle these resources. The move from upsert/abandon to create/delete in `5.0.0` had more knock-on effects than anticipated.

Related: https://github.com/hashicorp/terraform-provider-google/issues/9148

b/293142521 resulted in a documentation clarification: `If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput.` That should unblock resolution here.

Sending an explicit `"EMPTY"` to the API on create calls is likely required. Rather than `Computed`, we could consider setting the value to `"EMPTY"` in the import function, or in...

This error generally indicates the API is not strongly consistent, a violation of GCP's API guidance for management plane resources like ServiceAccountL https://google.aip.dev/121#strong-consistency. We do poll for the resource after...

> Because all the resources are going to be recognized as noncurrent immediately while the value of the condition is equal to 0. This shouldn't be the case- objects are...

Thanks! That's much worse, we're not sending `days_since_noncurrent_time` at all when it has a value of zero. Combined with `age` which gets sent when it has a value of zero,...

That works fine: ``` "lifecycle": { "rule": [ { "action": { "type": "Delete" }, "condition": { "age": 0, "daysSinceNoncurrentTime": 0 } } ] }, ```

@philip-harvey we're shipping a docs change immediately while we figure out the longer-term fix here (@NickElliot and @kautikdk are discussing offline). Mind giving https://github.com/GoogleCloudPlatform/magic-modules/pull/10626 a once-over to see if you...

Done in https://github.com/hashicorp/terraform-provider-google/pull/18118