Sam Levenick
Sam Levenick
Ok, good to know that the plugin framework will fix it. We are still a ways away from being able to convert existing resources to the plugin framework, so any...
I created https://github.com/hashicorp/terraform-plugin-sdk/issues/1236 because the original SDK issue was closed
Ah, this is the canonical issue, reopening
We've had some conversation offline, I'll summarize here: To support removal of a working field in favor for another field we need to have a version of the provider where...
> We had some notebooks running for months. We are using terraform 1.4.7 and google provider 4.84. We never had this issue before. For now, we added this field to...
@shawnsavour please file an issue against https://github.com/terraform-providers/terraform-provider-google
Hey @rvandegrift you can try the bigquery dataset IAM policy which wraps the dataset access resource as a workaround. It should be able to support your use case https://www.terraform.io/docs/providers/google/r/bigquery_dataset_iam.html
Ah, it looks like we need to wait on the go client to be merged to be able to test
This may be an unfortunate side effect of using Computed + Optional on the default_ttl field in the Terraform schema. Basically what I believe is happening is that default_ttl is...
> It looks like setting default_from_api: true isn't listed as a breaking change. Would it be worth it to set that on the current version? Yes, that would be a...