Brian Flad

I'm curious how this hasn't been more of an issue until now, but the `MarkComputedNilsAsUnknown` logic should likely be returning the untransformed value if it encounters a `tfsdk.ErrPathIsBlock` error, similar...

From an out-of-band conversation, please note that adding configuration to state upgrades to potentially update these "transparently" is not being considered upstream.

Another odd one, doing `d.Set("map_attribute", nil)` in the sdk would save a known empty map into the state, not null, at least for data sources.

This cropped up for us as well on a relatively small issue/PR count repository: > Error: You have exceeded a secondary rate limit. Please wait a few minutes before you...

Hi @jmgreg31 👋 What version of Terraform CLI are you using (`terraform version`)? There were similar reports in earlier 0.12 versions of the Terraform CLI.

Just to link the issues, see also https://github.com/hashicorp/terraform/issues/19932 for multiple provider instantiation.

This feature request is still valid and represents a rough edge for provider developers. Both terraform-plugin-sdk and terraform-plugin-framework support the ability to configure blocks and attributes with a deprecation message,...

Another validation implemented by `terraform-plugin-sdk` around this logic was checking if a `Required` attribute was configured. For resource and data source configurations, this should be safe to unilaterally validate as...

terraform-plugin-framework v0.9.0 and later include error diagnostics "Invalid Configuration for Read-Only Attribute" and "Missing Configuration for Required Attribute" during the `Validate*Config` RPCs to account for this. Another related part of...

Hi @apparentlymart 👋 Thank you for writing this up! I'm not sure we have a standardized/great way to track this in GitHub, however this is an enhancement we are considering...