Almost done

Author: rkoron007

content/terraform-docs-common/data/cloud-docs-nav-data.json

@@ -599,7 +599,7 @@
         "title": "Deploy infrastructure",
         "routes": [
           { "title": "Configuration versions", "path": "stacks/deploy/configuration-versions" },
-          { "title": "Review deployment plans", "path": "stacks/deploy/plans" }
+          { "title": "Review deployment plans", "path": "stacks/deploy/runs" }
         ]
       },
       {

content/terraform-docs-common/docs/cloud-docs/stacks/configure.mdx

@@ -12,26 +12,29 @@ This guide explains configuring a Stack’s name, description, project, and VCS
 
 To view a Stack and its configurations, you must also be a member of a team in your organization with one of the following permissions:
 
-* [Organization-level **Manage all projects**](/terraform/cloud-docs/users-teams-organizations/permissions#manage-all-projects) or higher  
+* [Organization-level **Manage all projects**](/terraform/cloud-docs/users-teams-organizations/permissions#manage-all-projects) or higher
 * [Project-level **Maintain**](/terraform/cloud-docs/users-teams-organizations/permissions#maintain) or higher
 
 ## Configure a Stack
 
 You can configure a Stack by performing the following steps:
 
 1. Sign in to [HCP Terraform](https://app.terraform.io) and select the organization that contains your Stack.
-1. In the navigation menu, click **Projects** under **Manage**.  
-1. Select the project containing your Stack.  
-1. Click **Stacks** in the navigation menu.  
-1. Select the Stack you want to configure.  
-1. Click **Stack settings** in the navigation menu.  
-1. Update any of the following settings:  
-   * Name
-   * Description
-   * Project, learn about [moving a Stack to another project](/terraform/cloud-docs/stacks/configure#move-a-stack-to-another-project).
-   * Version control settings, including:
-        * Stacks automatically trigger new plans when you push them to your repositories’ default branch. To deactivate this behavior,  uncheck **VCS Trigger Enabled**.  
-        * You can also configure Stacks to work from either a branch or tag-based workflow. 
+1. In the navigation menu, select **Projects** under **Manage**.
+1. Select the project containing your Stack.
+1. Select the Stack you want to configure.
+1. Select **Settings** in the side navigation.
+1. Update any of the following settings:
+   - Name
+   - Description
+   - Project, learn about [moving a Stack to another project](/terraform/cloud-docs/stacks/configure#move-a-stack-to-another-project).
+   - Version control settings, including:
+        - You can also view any linked VCS repository, add a VCS connection, change your source repository, or disconnect your Stack from VCS.
+        - Stacks automatically trigger new runs when you push a configuration change to a linked repository. To stop HCP Terraform from automatically fetching configuration changes, toggle **VCS Trigger Enabled**.
+        - You can enable or disable **Automatic speculative plans** to have your Stack create plan-only runs for pull requests to your linked VCS repository.
+        - You can also configure Stacks to work from either a branch or tag-based workflow.
+   - You can **Enable debug logging** to be able to download detailed logs from your Stack's runs.
+   - You can change your Stack's **Execution mode** to either **Remote** or **Agent**. Refer to [Change execution mode](#change-execution-mode) to learn more.
 1. Click **Save settings** to apply your changes.
 
 ## Move a Stack to another project
@@ -40,6 +43,12 @@ To move a Stack, you must have the **Manage all Projects** organization permissi
 
 Upstream Stacks must be in the same project as their downstream Stacks. Moving an upstream Stack to another project breaks any downstream Stack inputs, affecting future plans. Move upstream and downstream Stacks together to avoid disruptions. Learn more about [passing data from one Stack to another](/terraform/language/stacks/deploy/pass-data).
 
+### Change execution mode
+
+By default, HCP Terraform deploys infrastructure remotely using its own disposable virtual machines. This default execution mode is named **Remote** mode.
+
+[HCP Terraform agents](/terraform/cloud-docs/agents/) let HCP Terraform communicate with isolated, private, or on-premises infrastructure. After setting up an agent and an agent pool, you can choose to change a Stack's execution mode to **Agent** to have HCP Terraform execute your Stack runs on an agent. To learn more about setting up agents, refer to [Install and run agents](/terraform/cloud-docs/agents/agents).
+
 ## Next steps
 
-After configuring your Stack, you can learn more about how to [review your Stack’s deployment plans](/terraform/cloud-docs/stacks/deploy/plans) or [destroy your stack](/terraform/cloud-docs/stacks/destroy).
+After configuring your Stack, you can learn more about how to [review your Stack’s deployment runs](/terraform/cloud-docs/stacks/deploy/runs) or [destroy your Stack](/terraform/cloud-docs/stacks/destroy).

content/terraform-docs-common/docs/cloud-docs/stacks/create.mdx

@@ -40,17 +40,13 @@ Stacks live alongside workspaces in a project. To create a new Stack in HCP Terr
 1. Sign in to [HCP Terraform](https://app.terraform.io), and select the organization that contains your Stack.
 1. In the navigation menu, click **Projects** under **Manage**.
 1. Select the project where you want to create your Stack.
-1. In the project's navigation menu, select **Stacks**.
-1. Click **+ New stack**.
+1. Click **New**, then **Stack**.
 1. Select a version control provider from the list.
 1. Choose an organization and repository from the filterable list. If your repository is missing, enter its ID in the text field below the list. The list only displays the first 100 repositories from your VCS provider.
 1. Enter a new **Stack Name**.
     * The name must be unique within the project and can include letters, numbers, dashes (`-`), and underscores (`_`). We recommend using 90 characters or less for the name of your Stack.
 1. You can optionally add a description for your Stack.
-1. You can optionally adjust your version control settings by expanding **Advanced Options.**
-    * Stacks automatically trigger new plans when you push them to your repositories’ default branch. You can deactivate this by toggling the **VCS Trigger Enabled** setting.
-    * You can configure Stacks to use either a branch or tag-based workflow.
-    * By default, HCP Terraform fetches your Stack's configuration after creating your Stack. To fetch your Stack configuration manually, uncheck **Fetch configuration after HCP Terraform creates stack.**
+1. By default, HCP Terraform fetches your Stack's configuration after creating your Stack. To fetch your Stack configuration manually, uncheck **Fetch configuration after HCP Terraform creates stack**.
 1. Click **Create Stack**.
 
 ### Terraform CLI workflow
@@ -61,56 +57,60 @@ Stacks live alongside workspaces in an HCP Terraform project. To create a new St
 1. Run `terraform login` to authenticate with HCP Terraform. Alternatively, you can manually configure credentials in the CLI config file or through environment variables. Refer to [CLI Configuration](/terraform/cli/config/config-file#environment-variable-credentials) for details.
 1. Run the `terraform stacks create` command, replacing the placeholders with your organization name, project name, and desired Stack name:
 
-```shell-session
-$ terraform stacks create -organization <ORGANIZATION_NAME> -project <PROJECT_NAME> -stack-name <STACK_NAME>
-```
+    ```shell-session
+    $ terraform stacks create -organization <ORGANIZATION_NAME> -project <PROJECT_NAME> -stack-name <STACK_NAME>
+    ```
 
-A Stack name must be unique within the project and can include letters, numbers, dashes (`-`), and underscores (`_`). We recommend using 90 characters or less for the name of your Stack.
+    A Stack name must be unique within the project and can include letters, numbers, dashes (`-`), and underscores (`_`). We recommend using 90 characters or less for the name of your Stack.
 
-After running the command, you can view your new Stack in the HCP Terraform UI, or by running the `terraform stacks list` command:
+1. After running the command, you can view your new Stack in the HCP Terraform UI, or by running the `terraform stacks list` command:
 
-```shell-session
-$ terraform stacks list -organization <ORGANIZATION_NAME> -project <PROJECT_NAME>
-```
+    ```shell-session
+    $ terraform stacks list -organization <ORGANIZATION_NAME> -project <PROJECT_NAME>
+    ```
 
-After creating your Stack, you can push up your Stack component and deployment configuration files to create a new configuration version. Use the `terraform stacks configuration upload` command to manually upload your configuration files:
+1. After creating your Stack, you can push up your Stack component and deployment configuration files to create a new configuration version. Use the `terraform stacks configuration upload` command to manually upload your configuration files:
 
-```shell-session
-$ terraform stacks configuration upload -organization <ORGANIZATION_NAME> -project <PROJECT_NAME> -stack-name <STACK_NAME>
-```
+    ```shell-session
+    $ terraform stacks configuration upload -organization <ORGANIZATION_NAME> -project <PROJECT_NAME> -stack-name <STACK_NAME>
+    ```
 
-The Terraform CLI uploads the configuration files, and returns a new configuration version ID and sequence number:
+    The Terraform CLI uploads the configuration files, and returns a new configuration version ID and sequence number:
 
-```shell-session
-Uploading stack configuration...
+    ```shell-session
+    Uploading stack configuration...
 
-Configuration for Stack (id: 'st-MLQLSJVrdtGazA4aU') was uploaded
-Configuration ID: stc-6fSRO81hOzTPKMM
-Sequence Number: 1
+    Configuration for Stack (id: 'st-MLQLSJVrdtGazA4aU') was uploaded
+    Configuration ID: stc-6fSRO81hOzTPKMM
+    Sequence Number: 1
 
-See run at: <URL>
-```
+    See run at: <URL>
+    ```
 
-A Stack configuration version is a snapshot of all of the pieces that make up your Stack. Each configuration version creates a deployment run for every deployment of your Stack in order to implement the changes in that version. To learn more, refer to [Stack deployment runs](/terraform/cloud-docs/stacks/runs).
+    A Stack configuration version is a snapshot of all of the pieces that make up your Stack. Each configuration version creates a deployment run for every deployment of your Stack in order to implement the changes in that version. To learn more, refer to [Stack deployment runs](/terraform/cloud-docs/stacks/runs).
 
-After uploading your configuration, you can watch your Stack's configuration roll out using `terraform stacks configuration watch` to review a list of the deployment groups in your configuration:
+    After uploading your configuration, you can watch your Stack's configuration roll out using `terraform stacks configuration watch` to review a list of the deployment groups in your configuration:
 
-```shell-session
-$ terraform stacks configuration watch -organization <ORGANIZATION_NAME> -project <PROJECT_NAME>
+    ```shell-session
+    $ terraform stacks configuration watch -organization <ORGANIZATION_NAME> -project <PROJECT_NAME>
+    ```
 
+    The Terraform CLI then displays the status of each deployment group in your Stack:
 
-[Stack Id: st-MLQLSJVrdtGazA4aU]
-✓ Configuration: 'stc-6fSRO81hOzTPKMM'                    [Completed]    [11s]
-↻ Deployment Group: 'many_default'                        [Pending]      [58s]
-↻ Deployment Group: 'some_default'                        [Pending]      [58s]
-↻ Deployment Group: 'single_default'                      [Failed]       [6s]
+    ```shell-session
 
-Press q to quit
-```
+    [Stack Id: st-MLQLSJVrdtGazA4aU]
+    ✓ Configuration: 'stc-6fSRO81hOzTPKMM'                    [Completed]    [11s]
+    ↻ Deployment Group: 'many_default'                        [Pending]      [58s]
+    ↻ Deployment Group: 'some_default'                        [Pending]      [58s]
+    ↻ Deployment Group: 'single_default'                      [Failed]       [6s]
 
-You can continue to use the `terraform stacks` CLI commands to directly approve deployment runs, review configuration versions, and manage your Stack. To learn more, refer to the [`terraform stacks` commands](/terraform/cli/commands/stacks).
+    Press q to quit
+    ```
 
-Note that though you can create a Stack from the Terraform CLI, you cannot deploy a Stack locally. You can only deploy a Stack remotely in HCP Terraform, or by running your a Stack on a custom HCP Terraform agent. To learn more, refer to [Stack deployment runs](/terraform/cloud-docs/stacks/runs).
+    You can continue to use the `terraform stacks` CLI commands to directly approve deployment runs, review configuration versions, and manage your Stack. To learn more, refer to the [`terraform stacks` commands](/terraform/cli/commands/stacks).
+
+    Note that though you can create a Stack from the Terraform CLI, you cannot deploy a Stack locally. You can only deploy a Stack remotely in HCP Terraform, or by running your a Stack on a custom HCP Terraform agent. To learn more, refer to [Stack deployment runs](/terraform/cloud-docs/stacks/runs).
 
 ## Next steps