Add [email protected] documentation (#824)

* copy 1.15.x to new folder

* Framework: Add documentation for actions in plugin framework (#848)

* small changes to existing pages

* start with a one pager

* final updates to action page

* update validation page

* update general schema pages

* update attribute docs to be less specific about each schema

* update block types to be less specific

* updated type docs to be less specific

* split into two pages

* Apply suggestions from code review

Co-authored-by: Selena Goods <[email protected]>

---------

Co-authored-by: Selena Goods <[email protected]>

* updates to remove unlinked (#953)

* Framework: add documentation for list resources (#898)

* copy 1.15.x to new folder

* Framework: Add documentation for actions in plugin framework (#848)

* small changes to existing pages

* start with a one pager

* final updates to action page

* update validation page

* update general schema pages

* update attribute docs to be less specific about each schema

* update block types to be less specific

* updated type docs to be less specific

* split into two pages

* Apply suggestions from code review

Co-authored-by: Selena Goods <[email protected]>

---------

Co-authored-by: Selena Goods <[email protected]>

* add docs for list resources

* update nav info

* yaml spacing

* Apply suggestions from code review

---------

Co-authored-by: Austin Valle <[email protected]>
Co-authored-by: Selena Goods <[email protected]>

---------

Co-authored-by: Selena Goods <[email protected]>
Co-authored-by: stephybun <[email protected]>

Author: 3 people

content/terraform-plugin-framework/v1.16.x/data/plugin-framework-nav-data.json

@@ -0,0 +1,84 @@
+---
+page_title: Acceptance tests
+description: >-
+  Learn how to write acceptance tests for providers built on the framework.
+  Acceptance tests help ensure your provider works as expected by imitating
+  Terraform operations.
+---
+
+# Acceptance tests
+
+Implement provider resource and data source acceptance tests with the [terraform-plugin-testing module](/terraform/plugin/testing). These tests are designed to execute Terraform commands against real Terraform configurations, simulating practitioner experiences with creating, refreshing, updating, and deleting infrastructure.
+
+This page only describes requirements of using the testing module with a framework provider. Refer to the [testing module documentation](/terraform/plugin/testing) for additional information on all available functionality in tests.
+
+## Requirements
+
+The testing module must know how to reference your provider code before Terraform commands and configurations can succeed. This is achieved by pointing the testing module at a [provider server](/terraform/plugin/framework/provider-servers) which wraps your [provider](/terraform/plugin/framework/providers).
+
+Use one of the [`resource.TestCase` type](/terraform/plugin/testing/acceptance-tests/testcase) [`ProtoV6ProviderFactories` field](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-testing/helper/resource#TestCase.ProtoV6ProviderFactories) for [protocol version 6](/terraform/plugin/terraform-plugin-protocol#protocol-version-6) or [`ProtoV5ProviderFactories` field](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-testing/helper/resource#TestCase.ProtoV5ProviderFactories) for [protocol version 5](/terraform/plugin/terraform-plugin-protocol#protocol-version-5). It is only necessary to test with the single protocol version matching the production provider server, typically defined in the `main.go` file of the provider codebase.
+
+### Protocol Version 6
+
+Use the [`providerserver.NewProtocol6WithError`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/providerserver#NewProtocol6WithError) helper function to implement the provider server in the [`ProtoV6ProviderFactories` field](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-testing/helper/resource#TestCase.ProtoV6ProviderFactories).
+
+```go
+resource.Test(t, resource.TestCase{
+	ProtoV6ProviderFactories: map[string]func() (tfprotov6.ProviderServer, error) {
+		// newProvider is an example function that returns a provider.Provider
+		"examplecloud": providerserver.NewProtocol6WithError(newProvider()),
+	},
+	Steps: []resource.TestStep{/* ... */},
+})
+```
+
+### Protocol Version 5
+
+Use the [`providerserver.NewProtocol5WithError`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/providerserver#NewProtocol5WithError) helper function to implement the provider server in the [`ProtoV5ProviderFactories` field](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-testing/helper/resource#TestCase.ProtoV5ProviderFactories).
+
+```go
+resource.Test(t, resource.TestCase{
+	ProtoV5ProviderFactories: map[string]func() (tfprotov5.ProviderServer, error) {
+		// newProvider is an example function that returns a provider.Provider
+		"examplecloud": providerserver.NewProtocol5WithError(newProvider()),
+	},
+	Steps: []resource.TestStep{/* ... */},
+})
+```
+
+## Troubleshooting
+
+### No id found in attributes
+
+<Highlight>
+
+terraform-plugin-testing version 1.5.0 and later no longer require managed resources and data resources to implement the `id` attribute.
+
+</Highlight>
+
+In SDKv2, resources and data sources automatically included an implicit, root level `id` attribute. In the framework, the `id` attribute is not implicitly added.
+
+When testing resources and data sources without the `id` attribute, the acceptance testing framework will return errors such as:
+
+```text
+testing_new_config.go:111: no "id" found in attributes
+testing_new.go:53: no "id" found in attributes
+```
+
+To avoid this, add a root level `id` attribute to resource and data source schemas. Ensure the attribute value is appropriately [written to state](/terraform/plugin/framework/writing-state). Conventionally, `id` is a computed attribute that contains the identifier for the resource.
+
+For example, in the `Schema` method implementation of a [`datasource.DataSource`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource#DataSource) or [`resource.Resource`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource#Resource):
+
+```go
+func (r *ThingResource) Schema(ctx context.Context, req resource.SchemaRequest, resp *resource.SchemaResponse) {
+	resp.Schema = schema.Schema{
+		// ... potentially other schema configuration ...
+		Attributes: map[string]schema.Attribute{
+			// ... potentially other schema attributes ...
+			"id": schema.StringAttribute{
+				Computed: true,
+			},
+		},
+	}
+}
+```