Brian Flad

Hi @abergmeier 👋 Thank you for raising this and apologies for the lack of clarity around this. We are hoping that there will be a canonical terraform-plugin-sdk/v2 to terraform-plugin-framework migration...

@abergmeier gentle ping about the above.

https://github.com/hashicorp/terraform-plugin-framework/blob/main/docs/design/blocks.md describes it a little, but overall the Terraform CLI maintainers have determined that the practitioner experience is much better when working with attributes over blocks for a few reasons:...

An initial sdk/v2 to framework schema block migration guide has been published: https://www.terraform.io/plugin/framework/migrating/attributes-blocks/blocks 👍 Blocks were un-deprecated awhile ago and will have first-class support at least through version 1 of...

> I assume the framework is responsible for detecting and reporting duplicate type names in the resources/data sources returned via the slices? Indeed, yeah -- we won't get compiler time...

I'm going to transfer this issue over to terraform-website, so the documentation can be beside the GitHub Actions / `goreleaser` pieces we document today.

Would you be able to show how the attribute is being set into state (if it is) during `Create` and/or `Read`?

This may be similar to #201. Does explicitly setting the value `Null: true` help? e.g. something like: ```go if len(permissions) > 0 { data.Permissions = types.Map{ElemType: types.BoolType, Elems: permissions} }...

It may also be possible to use `Permissions map[string]bool` or something similar in the data type to workaround this.

Hey again @appilon 👋 Did you find a resolution for this situation or does either of the above help?