Brian Flad

The Terraform `Provider produced inconsistent result after apply` error with the details of `Root resource was present, but now absent.` should be removed by the changes in #260, however it...

Hi @tgoodsell-tempus 👋 Thank you for this feature request and @chrismarget-j for contributing to the discussion. Our main attention is elsewhere at the moment (finishing up Terraform 1.8 features such...

Upstream terraform-plugin-go's `(tftypes.Value).Type()` does not require the context: https://pkg.go.dev/github.com/hashicorp/[email protected]/tftypes#Value.Type

Hi folks 👋 Sorry for the delayed response here. The behavior of schema-based `Default` value handling occurs when the "object layer" containing the attribute is known (not null or unknown)....

@pksunkara I'm not aware of a way to do that today with existing framework functions/methods, but it may be possible to enhance the framework so that: - The object attribute...

Created https://github.com/hashicorp/terraform-plugin-framework/issues/777 with above. The proposal details are a little hazy/unclear since we'd need to avoid an import cycle, but I'm hopeful that it might be possible to work around...

Hi @Doridian 👋 Thank you for raising this concern. It appears that you're looking to simplify your provider development in cases where a data source lookup is fairly symmetrical to...

I'm going to split this feature request since `local_directory` is likely less controversial and has immediate use cases with checks.

Drive-by note about potentially including the deprecation _message_ that can be included in attribute definitions. Currently this information is not possible to inject into the documentation generation because this tool...

Related to https://github.com/hashicorp/terraform-provider-aws/issues/16796 for returning a better error message.