From d0cb88f0915f7f5e5983e5d56f4ad6bbbe4e0494 Mon Sep 17 00:00:00 2001 From: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> Date: Wed, 8 Dec 2021 13:49:58 -0500 Subject: [PATCH] Updates to TFC page in Language --- website/docs/language/settings/terraform-cloud.html.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/language/settings/terraform-cloud.html.md b/website/docs/language/settings/terraform-cloud.html.md index 4f536299d..fd1b94b71 100644 --- a/website/docs/language/settings/terraform-cloud.html.md +++ b/website/docs/language/settings/terraform-cloud.html.md @@ -11,6 +11,8 @@ The main module of a Terraform configuration can integrate with Terraform Cloud [CLI-driven run workflow](/docs/cloud/run/cli.html). You only need to configure these settings when you want to use Terraform CLI to interact with Terraform Cloud. Terraform Cloud ignores them when interacting with Terraform through version control or the API. +> **Hands On:** Try the [Migrate State to Terraform Cloud](https://learn.hashicorp.com/tutorials/terraform/cloud-migrate) tutorial on HashiCorp Learn. + You can configure the Terraform Cloud CLI integration by adding a nested `cloud` block within the top-level `terraform` block: @@ -26,6 +28,6 @@ terraform { } ``` -You cannot use the CLI integration and a [state backend](/docs/language/settings/backends/index.html) in the same configuration; the are mutually exclusive. A configuration can only provide one `cloud` block and the `cloud` block cannot refer to named values like input variables, locals, or data source attributes. +You cannot use the CLI integration and a [state backend](/docs/language/settings/backends/index.html) in the same configuration; they are mutually exclusive. A configuration can only provide one `cloud` block and the `cloud` block cannot refer to named values like input variables, locals, or data source attributes. Refer to [Using Terraform Cloud](/docs/cli/cloud/index.html) in the Terraform CLI docs for more information.