From 33e51aa644548eec68771333a1709428fac00295 Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Tue, 11 Nov 2025 15:51:39 -0800 Subject: [PATCH 1/4] remove beta callouts, update links for actions GA --- .../docs/cloud-docs/workspaces/run/manage.mdx | 17 +++++++++++++---- .../v1.13.x/docs/cli/commands/apply.mdx | 6 ------ .../v1.13.x/docs/cli/commands/plan.mdx | 6 ------ .../v1.13.x/docs/language/block/resource.mdx | 6 ------ .../docs/language/meta-arguments/index.mdx | 6 ------ .../docs/language/invoke-actions.mdx | 9 ++------- 6 files changed, 15 insertions(+), 35 deletions(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx b/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx index 7c4e133b27..c3801ec21e 100644 --- a/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx @@ -25,14 +25,23 @@ Click a run to go to its details page. The details page contains the following i - A timeline of events related to the run. - The output from both the `terraform plan` and `terraform apply` commands, if applicable. This output defaults to visible if the command is currently running and hidden if the command has finished. + + ### Action runs -@include 'beta.mdx' +HCP Terraform identifies runs that invoke actions on the run details page. Actions are preset operations built into providers that you can invoke to trigger automations outside of Terraform, such as Ansible playbooks and Lambda jobs. Refer to [Invoke an action](/terraform/language/invoke-actions) in the Terraform configuration language documentation for more information. + +HCP Terraform indicates how many actions the run invoked and adds **action:** labels to the **Plan** operation output and **Invoked:** labels to the **Apply** operation output. + +You can invoke actions either as part of a resource lifecycle configuration or manually target a specific action using the `-invoke` flag to a `terraformm apply` or `terraform plan` command. + + + +A Standard tier subscription is required to view details about actions that were invoked from the command line using the `-invoked` flag. Refer to the [Terraform pricing page](https://www.hashicorp.com/en/pricing?tab=terraform) for more information. -If a run invokes an action that is triggered as part of a resource lifecycle, HCP Terraform identifies them on the run details page. HCP Terraform indicates how many actions the run invoked and adds **action:** labels to the **Plan** operation output and **Invoked:** labels to the **Apply** operation output. + -Actions are preset operations built into providers that you can invoke to trigger automations outside of Terraform, such as Ansible playbooks and Lambda jobs. Refer to [Invoke an action](/terraform/language/v1.14.x/invoke-actions) in the Terraform configuration language documentation for more information. - + ## Interacting with Runs diff --git a/content/terraform/v1.13.x/docs/cli/commands/apply.mdx b/content/terraform/v1.13.x/docs/cli/commands/apply.mdx index 4a39c7a221..2c2abe1489 100644 --- a/content/terraform/v1.13.x/docs/cli/commands/apply.mdx +++ b/content/terraform/v1.13.x/docs/cli/commands/apply.mdx @@ -11,12 +11,6 @@ plan. > **Hands On:** Try the [Apply Terraform Configuration](/terraform/tutorials/cli/apply?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorial to learn how Terraform applies a configuration, how Terraform recovers from errors during apply, and common ways to use this command. - - -Terraform `v1.14.x (beta)` adds the `-invoke` flag, which lets you trigger actions outside of Terraform CRUD operations. Refer to the [Invoke an action](/terraform/language/v1.14.x/invoke-actions) beta documentation for more information. - - - ## Usage Usage: `terraform apply [options] [plan file]` diff --git a/content/terraform/v1.13.x/docs/cli/commands/plan.mdx b/content/terraform/v1.13.x/docs/cli/commands/plan.mdx index c380bef152..adb95884b3 100644 --- a/content/terraform/v1.13.x/docs/cli/commands/plan.mdx +++ b/content/terraform/v1.13.x/docs/cli/commands/plan.mdx @@ -10,12 +10,6 @@ description: >- The `terraform plan` command creates an execution plan, which lets you preview the changes that Terraform plans to make to your infrastructure. - - -Terraform `v1.14.x (beta)` adds the `-invoke` flag, which lets you trigger actions outside of Terraform CRUD operations. Refer to the [Invoke an action](/terraform/language/v1.14.x/invoke-actions) beta documentation for more information. - - - ## Introduction By default, Terraform performs the following operations when it creates a plan: diff --git a/content/terraform/v1.13.x/docs/language/block/resource.mdx b/content/terraform/v1.13.x/docs/language/block/resource.mdx index 3c21e44f46..bb3132ac2c 100644 --- a/content/terraform/v1.13.x/docs/language/block/resource.mdx +++ b/content/terraform/v1.13.x/docs/language/block/resource.mdx @@ -8,12 +8,6 @@ description: >- The `resource` block defines a piece of infrastructure and specifies the settings for Terraform to create it with. The arguments that an individual resource supports are determined by the provider. Refer to the provider documentation for more information about specific resource configuration. - - -Terraform `v1.14.x (beta)` supports the `action_trigger` block, which you can add to resource configurations to trigger actions outside of Terraform CRUD operations. Refer to the [Invoke an action](/terraform/language/v1.14.x/invoke-actions) beta documentation for more information. - - - ## Configuration model The `resource` block supports the following arguments: diff --git a/content/terraform/v1.13.x/docs/language/meta-arguments/index.mdx b/content/terraform/v1.13.x/docs/language/meta-arguments/index.mdx index 60221d6c63..0cf212dcd5 100644 --- a/content/terraform/v1.13.x/docs/language/meta-arguments/index.mdx +++ b/content/terraform/v1.13.x/docs/language/meta-arguments/index.mdx @@ -9,12 +9,6 @@ Meta-arguments are a class of arguments built into the Terraform configuration l The provider developer determines resource-specific arguments, but all resources support meta-arguments that let you manage resources' infrastructure lifecycle, including destruction behavior, preventing destruction, and establishing dependencies between resources. Terraform provides the following meta-arguments. - - -Terraform `v1.14.x (beta)` adds the `action_trigger` meta-argument, which lets you trigger actions that extend Terraform CRUD operations. Refer to the [Invoke an action](/terraform/language/v1.14.x/invoke-actions) beta documentation for more information. - - - ## `depends_on` The `depends_on` meta-argument instructs Terraform to complete all actions on the dependency object, including `read` operations, before performing actions on the object declaring the dependency. Use the `depends_on` argument to explicitly set the order in which Terraform creates resources. Refer to the [`depends_on` reference](/terraform/language/meta-arguments/depends_on) for details. diff --git a/content/terraform/v1.14.x (rc)/docs/language/invoke-actions.mdx b/content/terraform/v1.14.x (rc)/docs/language/invoke-actions.mdx index cee5820d95..bed8103b4c 100644 --- a/content/terraform/v1.14.x (rc)/docs/language/invoke-actions.mdx +++ b/content/terraform/v1.14.x (rc)/docs/language/invoke-actions.mdx @@ -7,19 +7,14 @@ description: Learn how to invoke actions defined in Terraform configuration lang Actions are preset operations built into providers that let Terraform perform day-two operations. Invoke actions to trigger automations outside of Terraform, such as Ansible playbooks and Lambda jobs. Actions do not affect resource state. -@include 'beta.mdx' - ## Overview Declare an `action` block in your Terraform configuration and apply your configuration or use the Terraform CLI to invoke the action. You can configure actions that aren't directly associated with a resource. These actions don't change the state of resources managed by Terraform. ## Requirements -Provider authors implement actions for them to be available. To check for actions available in your provider, refer to the provider documentation. Actions are available in the following providers on the Terraform Registry: +Provider develoeprs must implement actions for them to be available. Refer to the provider documentation for information about actions that may be available in your provider. -- [aws](https://registry.terraform.io/providers/hashicorp/aws/latest) -- [azurerm](https://registry.terraform.io/providers/hashicorp/azurerm/latest) - ### HCP Terraform To monitor actions in HCP Terraform, you must configure a connection to HCP Terraform in your Terraform configuration. Refer to [Connect to HCP Terraform](/terraform/cli/cloud/settings) for instructions. @@ -128,4 +123,4 @@ Because the `event` argument includes `after_update`, Terraform also updates th ## View actions in HCP Terraform -If your workspace is connected to your HCP Terraform organization, you can monitor action runs in HCP Terraform. Refer to [Action runs](/terraform/cloud-docs/run/manage#action-runs) in the HCP Terraform documentation for more information. +If your workspace is connected to your HCP Terraform organization, you can monitor action runs in HCP Terraform. Refer to [Action runs](/terraform/cloud-docs/workspaces/run/manage#action-runs) in the HCP Terraform documentation for more information. From a93558269f7551e6922b15a17792c91e576833bd Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Wed, 12 Nov 2025 08:51:00 -0800 Subject: [PATCH 2/4] add 'actions' alias to lifecycle meta-arg --- content/terraform/v1.14.x (rc)/data/language-nav-data.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/terraform/v1.14.x (rc)/data/language-nav-data.json b/content/terraform/v1.14.x (rc)/data/language-nav-data.json index f1a088ce7f..b3116bcf7f 100644 --- a/content/terraform/v1.14.x (rc)/data/language-nav-data.json +++ b/content/terraform/v1.14.x (rc)/data/language-nav-data.json @@ -392,8 +392,7 @@ "routes": [ { "title": "Overview", - "path": "meta-arguments", - "alias": "actions" + "path": "meta-arguments" }, { "title": "count", @@ -409,7 +408,8 @@ }, { "title": "lifecycle", - "path": "meta-arguments/lifecycle" + "path": "meta-arguments/lifecycle", + "alias": "actions" }, { "title": "provider", From eee986a285a1f1a8af373c0d36d36f29e8716f2b Mon Sep 17 00:00:00 2001 From: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> Date: Wed, 12 Nov 2025 14:01:33 -0800 Subject: [PATCH 3/4] Apply suggestions from code review --- .../docs/cloud-docs/workspaces/run/manage.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx b/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx index c3801ec21e..e322f8ce69 100644 --- a/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/workspaces/run/manage.mdx @@ -33,11 +33,11 @@ HCP Terraform identifies runs that invoke actions on the run details page. Actio HCP Terraform indicates how many actions the run invoked and adds **action:** labels to the **Plan** operation output and **Invoked:** labels to the **Apply** operation output. -You can invoke actions either as part of a resource lifecycle configuration or manually target a specific action using the `-invoke` flag to a `terraformm apply` or `terraform plan` command. +You can invoke actions either as part of a resource lifecycle configuration or manually target a specific action using the `-invoke` flag to a `terraform apply` or `terraform plan` command. -A Standard tier subscription is required to view details about actions that were invoked from the command line using the `-invoked` flag. Refer to the [Terraform pricing page](https://www.hashicorp.com/en/pricing?tab=terraform) for more information. +A Standard tier subscription is required to use the `-invoke` flag to execute an action and to view details about action runs that were invoked from the command line using the `-invoke` flag. Refer to the [Terraform pricing page](https://www.hashicorp.com/en/pricing?tab=terraform) for more information. From 4769813dac8c9ec078ac66c1d3a075fae3ce01b0 Mon Sep 17 00:00:00 2001 From: Roniece Date: Mon, 17 Nov 2025 15:07:10 -0500 Subject: [PATCH 4/4] Add 'action_only' run type description for HCPT --- content/terraform-docs-common/docs/cloud-docs/api-docs/run.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/content/terraform-docs-common/docs/cloud-docs/api-docs/run.mdx b/content/terraform-docs-common/docs/cloud-docs/api-docs/run.mdx index e0f402ee66..a4a0f1e8a3 100644 --- a/content/terraform-docs-common/docs/cloud-docs/api-docs/run.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/api-docs/run.mdx @@ -98,6 +98,7 @@ The run operation specifies the Terraform execution mode. You can reference the | `refresh_only` | The run should update Terraform state, but not make changes to resources. | | `destroy` | The run should destroy all objects, regardless of configuration changes. | | `empty_apply` | The run should perform an apply with no changes to resources. This is most commonly used to [upgrade terraform state versions](/terraform/cloud-docs/workspaces/state#upgrading-state). | +| `action_only` | The run is a `refresh_only` run that contains at least one [action invocation](/terraform/plugin/framework/actions). It updates state but does not create, change, or destroy resources. | ### Run Sources