Brian Flad

After some further investigation this morning, the framework cannot just automatically run the Computed attribute configuration null to unknown logic after plan modifiers, since it would undo some of the...

Another potential item to consider is if there is any state issues when migrating between frameworks as the schema will be represented slightly differently to Terraform CLI. This may require...

It looks like providers migrating from sdk/v2 to framework, but remaining on protocol version 5, do actually need something to be done here otherwise Terraform will report back `empty list...

For what it is worth, I initially lean towards documenting this in the migration documentation (items one and two above). For most providers, I think the preference will be to...

Initial sdk/v2 to framework migration guide for this topic has been published: https://www.terraform.io/plugin/framework/migrating/attributes-blocks/blocks-computed

I'll review once #231 is sorted and this change set is clearer. 👍

@paddycarver I _think_ we're finally at a place where we can work on this after a lot of refactoring. Do you have interest in the implementation still?

Ha, I just ran into this myself while working on the scaffolding repository. It is definitely easy to get this wrong.

The next version of the framework will begin returning error diagnostics such as the following when null/unknown values cannot be handled when getting schema-based data: ```text Error: Value Conversion Error...

Hey @appilon 👋 Just to drop a quick note -- this will require upstream changes in Terraform CLI, the protocol, and terraform-plugin-go before this it can potentially be implemented. We...