Documentation for mapping between SDKv2 and the Framework

[bendbennett]

Closes: #664
Closes: #659
Closes: #657
Closes: #650

[remyleone]

Would some html be useful here to have a list for the cases where there are several translation available: https://stackoverflow.com/questions/19950648/how-to-write-lists-inside-a-markdown-table

[bflad]

I'm not sure how well our Markdown rendering engine for the website plays with intermixed HTML/Markdown syntax. Another option here could be having separate table columns for data source, provider, and resource to prevent the listing in general.

[bendbennett]

Have split into 3 columns for data source, provider and resource.

[bflad]

I'm wondering if we might also want a table on https://developer.hashicorp.com/terraform/plugin/framework/migrating/attributes-blocks/fields that accounts for all the schema.Schema since that may be where folks first wind up when looking for this type of information. That framework side of that table could point folks to either the direct answer (e.g. Required for Required) or link to the other migration pages:

SDK Schema Field	Framework
Required	Required field on attribute
ValidateFunc	Predefined Validators and Custom Validators

It may also be worth considering something similar for https://developer.hashicorp.com/terraform/plugin/framework/migrating/attributes-blocks/blocks since they have a differing migration path -- e.g. #650

[bflad]

I think this is shaping up nicely so far!

[bflad]

I think it might be good to call out that any schema.Resource in Elem should refer to the blocks documentation instead. 👍

[bendbennett]

Updated to include call out.

[bflad]

Since there are a variety of differences between blocks and attributes, I think this page might warrant its own table. The prior SDK allowed developers to do unsupported things, like declare Sensitive on blocks (hashicorp/terraform-plugin-sdk#819) and we already have special callouts in paragraph form about Computed and Required. Therefore I think we should walk through the various fields and how they relate to blocks:

SDK Schema Field	Framework
Computed	Link to computed block page
Optional	N/A - no implementation required
Required	listvalidator.IsRequired() and setvalidator.IsRequired() (let's omit any discussion on single nested blocks, they weren't possible to declare before)
Sensitive	N/A - only supported on attributes

etc. 😄

[bendbennett]

Have added a table into the Blocks page.

[bflad]

This looks really good to me 🚀 Nice work mapping everything out.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.