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]>

Author: austinvalle

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

@@ -306,6 +306,19 @@
       }
     ]
   },
+  {
+    "title": "Actions",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "actions"
+      },
+      {
+        "title": "Implementation",
+        "path": "actions/implementation"
+      }
+    ]
+  },
   {
     "title": "Handling Data",
     "routes": [

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/actions/implementation.mdx

@@ -0,0 +1,34 @@
+---
+page_title: Actions overview
+description: >-
+  Actions allow providers to expose side-effects that interact with remote systems.
+  Practitioners can use actions to express workflows that don't strictly fit into typical
+  CRUD resource management. Learn how the plugin framework can help you implement actions.
+---
+
+# Actions
+
+<Highlight>
+
+Action support is in technical preview and offered without compatibility promises until Terraform 1.14 is generally available.
+
+</Highlight>
+
+Actions are an abstraction that allow providers to expose side-effects that interact with remote systems. Practitioners
+can use actions to express workflows that don't strictly fit into typical [CRUD resource management](/terraform/plugin/framework/resources),
+such as disaster recovery or ad-hoc maintenance. Actions can be invoked directly with the Terraform CLI or with
+a trigger in a plan/apply workflow.
+
+## Action types
+
+Each action in a provider has a statically defined action type in the [schema](/terraform/plugin/framework/actions/implementation#schema-method), which informs Terraform how the action can be used
+by the practitioner and what effect the action can have on [resource state](/terraform/plugin/framework/handling-data/terraform-concepts#state).
+Currently, the only available action type is:
+
+- [Unlinked](/terraform/plugin/framework/actions/implementation#unlinked-action) - An action type that cannot cause changes to state.
+
+Action types that can modify resource state are not available in Terraform 1.14, but are planned for future releases.
+
+## Implementation
+
+Learn about how to [implement code](/terraform/plugin/framework/actions/implementation) for an action in the framework.

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/actions/index.mdx

@@ -8,13 +8,7 @@ description: >-
 
 # Ephemeral resources
 
-<Highlight>
-
-Ephemeral resource support is in technical preview and offered without compatibility promises until Terraform 1.10 is generally available.
-
-</Highlight>
-
-[Ephemeral resources](/terraform/language/v1.10.x/resources/ephemeral) are an abstraction that allows Terraform to reference external data. Unlike [data sources](/terraform/language/data-sources), Terraform guarantees that ephemeral resource data will not be persisted in plan or state artifacts. The data produced by an ephemeral resource can only be referenced in [specific ephemeral contexts](/terraform/language/v1.10.x/resources/ephemeral#referencing-ephemeral-resources) or Terraform will throw an error.
+[Ephemeral resources](/terraform/language/resources/ephemeral) are an abstraction that allows Terraform to reference external data. Unlike [data sources](/terraform/language/data-sources), Terraform guarantees that ephemeral resource data will not be persisted in plan or state artifacts. The data produced by an ephemeral resource can only be referenced in [specific ephemeral contexts](/terraform/language/resources/ephemeral#referencing-ephemeral-resources) or Terraform will throw an error. Ephemeral resources are supported in Terraform 1.10 and later.
 
 This page describes the basic implementation details required for supporting an ephemeral resource within the provider. Ephemeral resources, as a part of their lifecycle, must implement:
 

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/ephemeral-resources/index.mdx

@@ -19,14 +19,14 @@ resource "examplecloud_thing" "example" {
 
 ## Schema Definition
 
-Use one of the following attribute types to directly add a bool value to a [schema](/terraform/plugin/framework/handling-data/schemas) or [nested attribute type](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types):
+Boolean attributes are supported in all framework [schemas](/terraform/plugin/framework/handling-data/schemas) and [nested attribute types](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types).
+Each concept (provider, resource, data source, etc.) has a separate `BoolAttribute` which can be used to add a bool value to a schema. For example (non-exhaustive):
 
 | Schema Type | Attribute Type |
 |-------------|----------------|
 | [Data Source](/terraform/plugin/framework/data-sources) | [`schema.BoolAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource/schema#BoolAttribute) |
 | [Provider](/terraform/plugin/framework/providers) | [`schema.BoolAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/provider/schema#BoolAttribute) |
 | [Resource](/terraform/plugin/framework/resources) | [`schema.BoolAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource/schema#BoolAttribute) |
-| [Ephemeral Resource](/terraform/plugin/framework/ephemeral-resources) | [`schema.BoolAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/ephemeral/schema#BoolAttribute) |
 
 In this example, a resource schema defines a top level required bool attribute named `example_attribute`:
 

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/handling-data/attributes/bool.mdx

@@ -48,14 +48,14 @@ resource "examplecloud_thing" "example" {
 
 ## Schema Definition
 
-Use one of the following attribute types to directly add a dynamic value to a [schema](/terraform/plugin/framework/handling-data/schemas) or a [single nested attribute type](/terraform/plugin/framework/handling-data/attributes/single-nested):
+Dynamic attributes are supported in most framework [schemas](/terraform/plugin/framework/handling-data/schemas) and the [single nested attribute type](/terraform/plugin/framework/handling-data/attributes/single-nested).
+Each concept (provider, resource, data source, etc.) has a separate `DynamicAttribute` which can be used to add a dynamic value to a schema. For example (non-exhaustive):
 
 | Schema Type | Attribute Type |
 |-------------|----------------|
 | [Data Source](/terraform/plugin/framework/data-sources) | [`schema.DynamicAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource/schema#DynamicAttribute) |
 | [Provider](/terraform/plugin/framework/providers) | [`schema.DynamicAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/provider/schema#DynamicAttribute) |
 | [Resource](/terraform/plugin/framework/resources) | [`schema.DynamicAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource/schema#DynamicAttribute) |
-| [Ephemeral Resource](/terraform/plugin/framework/ephemeral-resources) | [`schema.DynamicAttribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/ephemeral/schema#DynamicAttribute) |
 
 In this example, a resource schema defines a top level required dynamic attribute named `example_attribute`:
 

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/handling-data/attributes/dynamic.mdx

@@ -25,14 +25,14 @@ resource "examplecloud_thing" "example" {
 
 ## Schema Definition
 
-Use one of the following attribute types to directly add a float32 value to a [schema](/terraform/plugin/framework/handling-data/schemas) or [nested attribute type](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types):
+Float32 attributes are supported in all framework [schemas](/terraform/plugin/framework/handling-data/schemas) and [nested attribute types](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types).
+Each concept (provider, resource, data source, etc.) has a separate `Float32Attribute` which can be used to add a float32 value to a schema. For example (non-exhaustive):
 
 | Schema Type | Attribute Type |
 |-------------|----------------|
 | [Data Source](/terraform/plugin/framework/data-sources) | [`schema.Float32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource/schema#Float32Attribute) |
 | [Provider](/terraform/plugin/framework/providers) | [`schema.Float32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/provider/schema#Float32Attribute) |
 | [Resource](/terraform/plugin/framework/resources) | [`schema.Float32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource/schema#Float32Attribute) |
-| [Ephemeral Resource](/terraform/plugin/framework/ephemeral-resources) | [`schema.Float32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/ephemeral/schema#Float32Attribute) |
 
 In this example, a resource schema defines a top level required float32 attribute named `example_attribute`:
 

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/handling-data/attributes/float32.mdx

@@ -25,14 +25,14 @@ resource "examplecloud_thing" "example" {
 
 ## Schema Definition
 
-Use one of the following attribute types to directly add a float64 value to a [schema](/terraform/plugin/framework/handling-data/schemas) or [nested attribute type](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types):
+Float64 attributes are supported in all framework [schemas](/terraform/plugin/framework/handling-data/schemas) and [nested attribute types](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types).
+Each concept (provider, resource, data source, etc.) has a separate `Float64Attribute` which can be used to add a float64 value to a schema. For example (non-exhaustive):
 
 | Schema Type | Attribute Type |
 |-------------|----------------|
 | [Data Source](/terraform/plugin/framework/data-sources) | [`schema.Float64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource/schema#Float64Attribute) |
 | [Provider](/terraform/plugin/framework/providers) | [`schema.Float64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/provider/schema#Float64Attribute) |
 | [Resource](/terraform/plugin/framework/resources) | [`schema.Float64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource/schema#Float64Attribute) |
-| [Ephemeral Resource](/terraform/plugin/framework/ephemeral-resources) | [`schema.Float64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/ephemeral/schema#Float64Attribute) |
 
 In this example, a resource schema defines a top level required float64 attribute named `example_attribute`:
 

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/handling-data/attributes/float64.mdx

@@ -25,14 +25,14 @@ resource "examplecloud_thing" "example" {
 
 ## Schema Definition
 
-Use one of the following attribute types to directly add a int32 value to a [schema](/terraform/plugin/framework/handling-data/schemas) or [nested attribute type](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types):
+Int32 attributes are supported in all framework [schemas](/terraform/plugin/framework/handling-data/schemas) and [nested attribute types](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types).
+Each concept (provider, resource, data source, etc.) has a separate `Int32Attribute` which can be used to add an int32 value to a schema. For example (non-exhaustive):
 
 | Schema Type | Attribute Type |
 |-------------|----------------|
 | [Data Source](/terraform/plugin/framework/data-sources) | [`schema.Int32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource/schema#Int32Attribute) |
 | [Provider](/terraform/plugin/framework/providers) | [`schema.Int32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/provider/schema#Int32Attribute) |
 | [Resource](/terraform/plugin/framework/resources) | [`schema.Int32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource/schema#Int32Attribute) |
-| [Ephemeral Resource](/terraform/plugin/framework/ephemeral-resources) | [`schema.Int32Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/ephemeral/schema#Int32Attribute) |
 
 In this example, a resource schema defines a top level required int32 attribute named `example_attribute`:
 

content/terraform-plugin-framework/v1.16.x/docs/plugin/framework/handling-data/attributes/int32.mdx

@@ -25,14 +25,14 @@ resource "examplecloud_thing" "example" {
 
 ## Schema Definition
 
-Use one of the following attribute types to directly add a int64 value to a [schema](/terraform/plugin/framework/handling-data/schemas) or [nested attribute type](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types):
+Int64 attributes are supported in all framework [schemas](/terraform/plugin/framework/handling-data/schemas) and [nested attribute types](/terraform/plugin/framework/handling-data/attributes#nested-attribute-types).
+Each concept (provider, resource, data source, etc.) has a separate `Int64Attribute` which can be used to add an int64 value to a schema. For example (non-exhaustive):
 
 | Schema Type | Attribute Type |
 |-------------|----------------|
 | [Data Source](/terraform/plugin/framework/data-sources) | [`schema.Int64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/datasource/schema#Int64Attribute) |
 | [Provider](/terraform/plugin/framework/providers) | [`schema.Int64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/provider/schema#Int64Attribute) |
 | [Resource](/terraform/plugin/framework/resources) | [`schema.Int64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource/schema#Int64Attribute) |
-| [Ephemeral Resource](/terraform/plugin/framework/ephemeral-resources) | [`schema.Int64Attribute`](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/ephemeral/schema#Int64Attribute) |
 
 In this example, a resource schema defines a top level required int64 attribute named `example_attribute`: