Rename stack block folders

Author: rkoron007

content/terraform/v1.13.x/data/language-nav-data.json

@@ -320,25 +320,25 @@
     "title": "Stack blocks",
     "routes": [
       { "title": "Component configuration", "routes": [
-        { "title": "Overview", "path": "block/stack/component_configuration" },
-        { "title": "component", "path": "block/stack/component_configuration/component" },
-        { "title": "required_providers", "path": "block/stack/component_configuration/required_providers" },
-        { "title": "provider", "path": "block/stack/component_configuration/provider" },
-        { "title": "variable", "path": "block/stack/component_configuration/variable" },
-        { "title": "output", "path": "block/stack/component_configuration/output" },
-        { "title": "removed", "path": "block/stack/component_configuration/removed" },
+        { "title": "Overview", "path": "block/stack/tfcomponent" },
+        { "title": "component", "path": "block/stack/tfcomponent/component" },
+        { "title": "required_providers", "path": "block/stack/tfcomponent/required_providers" },
+        { "title": "provider", "path": "block/stack/tfcomponent/provider" },
+        { "title": "variable", "path": "block/stack/tfcomponent/variable" },
+        { "title": "output", "path": "block/stack/tfcomponent/output" },
+        { "title": "removed", "path": "block/stack/tfcomponent/removed" },
         { "title": "locals", "href": "block/locals" }
       ]
       },
       { "title": "Deployment configuration", "routes": [
-        { "title": "Overview", "path": "block/stack/deploy" },
-        { "title": "deployment", "path": "block/stack/deploy/deployment" },
-        { "title": "deployment_group", "path": "block/stack/deploy/deployment_group" },
-        { "title": "deployment_auto_approve", "path": "block/stack/deploy/deployment_auto_approve" },
-        { "title": "identity_token", "path": "block/stack/deploy/identity_token" },
-        { "title": "store", "path": "block/stack/deploy/store" },
-        { "title": "publish_output", "path": "block/stack/deploy/publish_output" },
-        { "title": "upstream_input", "path": "block/stack/deploy/upstream_input" },
+        { "title": "Overview", "path": "block/stack/tfdeploy" },
+        { "title": "deployment", "path": "block/stack/tfdeploy/deployment" },
+        { "title": "deployment_group", "path": "block/stack/tfdeploy/deployment_group" },
+        { "title": "deployment_auto_approve", "path": "block/stack/tfdeploy/deployment_auto_approve" },
+        { "title": "identity_token", "path": "block/stack/tfdeploy/identity_token" },
+        { "title": "store", "path": "block/stack/tfdeploy/store" },
+        { "title": "publish_output", "path": "block/stack/tfdeploy/publish_output" },
+        { "title": "upstream_input", "path": "block/stack/tfdeploy/upstream_input" },
         {
           "title": "locals",
           "href": "block/locals"

content/terraform/v1.13.x/docs/language/block/stack/deploy/index.mdx

@@ -12,11 +12,11 @@ Use the `component` block to source the individual modules that make up your Sta
 The `component` block defines the infrastructure to include in your Stack. Each Stack requires at least one `component` block, and you must add a `component` block to your configuration for every module you want to include in your Stack.
 
 Each component sources a Terraform module, can receive input variables, and accepts providers that you declare at the Stack level. You can define the following configuration blocks in a `tfcomponent.hcl` file:
-- Use the [`required_providers` block](/terraform/language/block/stack/configuration/required_providers) to declare which providers your component configuration requires so that Terraform can install and use them.
-- Use the [`provider` block](/terraform/language/block/stack/configuration/provider) to configure providers, then pass that configuration to a component.
-- Use the [`removed` block](/terraform/language/block/stack/configuration/removed) to define the components you want to remove from your Stack.
-- Use the [`variable` block](/terraform/language/block/variable) to define input variables for a Stack.
-- Use the [`output` block](/terraform/language/block/output) to define outputs that you want to refer to in the HCP Terraform UI.
+- Use the [`required_providers` block](/terraform/language/block/stack/tfcomponent/required_providers) to declare which providers your component configuration requires so that Terraform can install and use them.
+- Use the [`provider` block](/terraform/language/block/stack/tfcomponent/provider) to configure providers, then pass that configuration to a component.
+- Use the [`removed` block](/terraform/language/block/stack/tfcomponent/removed) to define the components you want to remove from your Stack.
+- Use the [`variable` block](/terraform/language/block/stack/tfcomponent/variable) to define input variables for a Stack.
+- Use the [`output` block](/terraform/language/block/stack/tfcomponent/output) to define outputs that you want to refer to in the HCP Terraform UI.
 - Use the [`locals` block](/terraform/language/block/locals) to define local values that you can use within your component configuration.
 
 ## Configuration model

content/terraform/v1.13.x/docs/language/block/stack/component_configuration/component.mdx renamed to content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/component.mdx

@@ -19,10 +19,10 @@ Each Stack requires at least one `component` block, and you must add a `componen
 
 You can define the following blocks in component configuration files:
 
-- The [`component`](/terraform/language/block/stack/configuration/component) block sources individual modules that make up your Stack. Each component receives input variables and accepts providers that you declare at the Stack level.
-- The [`required_providers`](/terraform/language/block/stack/configuration/required_providers) block declares which providers your component configuration requires so that Terraform can install and use them.
-- The [`provider`](/terraform/language/block/stack/configuration/provider) block configures providers and passes that configuration to components.
-- The [`removed`](/terraform/language/block/stack/configuration/removed) block defines components you want to remove from your Stack while ensuring proper cleanup of resources.
-- The [`variable`](/terraform/language/block/stack/configuration/variable) block defines input variables that your deployments can set with different values.
-- The [`output`](/terraform/language/block/stack/configuration/output) block defines values to expose in the HCP Terraform UI and to make available to deployments.
+- The [`component`](/terraform/language/block/stack/tfcomponent/component) block sources individual modules that make up your Stack. Each component receives input variables and accepts providers that you declare at the Stack level.
+- The [`required_providers`](/terraform/language/block/stack/tfcomponent/required_providers) block declares which providers your component configuration requires so that Terraform can install and use them.
+- The [`provider`](/terraform/language/block/stack/tfcomponent/provider) block configures providers and passes that configuration to components.
+- The [`removed`](/terraform/language/block/stack/tfcomponent/removed) block defines components you want to remove from your Stack while ensuring proper cleanup of resources.
+- The [`variable`](/terraform/language/block/stack/tfcomponent/variable) block defines input variables that your deployments can set with different values.
+- The [`output`](/terraform/language/block/stack/tfcomponent/output) block defines values to expose in the HCP Terraform UI and to make available to deployments.
 - The [`locals`](/terraform/language/block/locals) block defines local values that you can reference within your component configuration.

content/terraform/v1.14.x (alpha)/docs/language/block/stack/component_configuration/index.mdx renamed to content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/index.mdx

@@ -154,8 +154,8 @@ You can only reference ephemeral variables from specific contexts or Terraform t
 - In a managed resource [write-only argument](/terraform/language/resources/ephemeral/write-only)
 - In an [`ephemeral` block](/terraform/language/block/ephemeral)
 - In the [`locals` block](/terraform/language/block/locals)
-- In other [`variable` blocks with the `ephemeral` argument set to `true`](/terraform/language/block/stack/configuration/variable#ephemeral)
-- In other [`output` blocks with the `ephemeral` argument set to `true`](/terraform/language/block/stack/configuration/output#ephemeral)
+- In other [`variable` blocks with the `ephemeral` argument set to `true`](/terraform/language/block/stack/tfcomponent/variable#ephemeral)
+- In other [`output` blocks with the `ephemeral` argument set to `true`](/terraform/language/block/stack/tfcomponent/output#ephemeral)
 - Configuring [providers in the `provider` block](/terraform/language/functions/terraform-applying)
 - In [provisioner](/terraform/language/resources/provisioners/syntax) and [connection](/terraform/language/resources/provisioners/connection) blocks
 

content/terraform/v1.14.x (alpha)/docs/language/block/stack/component_configuration/output.mdx renamed to content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/output.mdx

@@ -11,15 +11,15 @@ If you are declaring a `provider` block in a traditional Terraform configuration
 
 ## Background
 
-In component configurations, you must declare a provider in the [`required_providers`](/terraform/language/block/stack/configuration/required_providers) block at the top level of your `tfcomponent.hcl` file before you can use that provider.
+In component configurations, you must declare a provider in the [`required_providers`](/terraform/language/block/stack/tfcomponent/required_providers) block at the top level of your `tfcomponent.hcl` file before you can use that provider.
 
 After your provider declaration, use the `provider` block to further configure your providers. Unlike traditional Terraform configurations, `provider` blocks in component configurations support the following:
 
 - The `for_each` meta-argument for dynamic provider configurations.
 - Defining provider aliases in the block header.
 - Using a `config` block to pass in provider arguments.
 
-After configuring your providers, pass them to your Stack's [`component` blocks using the `providers` argument](/terraform/language/block/stack/configuration/component#providers). Passing configurations directly to components ensures that every component in your Stack uses the same provider configuration. To learn more and view examples, refer to [Declare providers](/terraform/language/stacks/component/declare-providers).
+After configuring your providers, pass them to your Stack's [`component` blocks using the `providers` argument](/terraform/language/block/stack/tfcomponent/component#providers). Passing configurations directly to components ensures that every component in your Stack uses the same provider configuration. To learn more and view examples, refer to [Declare providers](/terraform/language/stacks/component/declare-providers).
 
 ## Configuration model
 

content/terraform/v1.14.x (alpha)/docs/language/block/stack/component_configuration/provider.mdx renamed to content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/provider.mdx

@@ -63,7 +63,7 @@ required_providers {
 
 ### `<PROVIDER_NAME>`
 
-Each provider declaration uses the provider name as a key that maps to a block with the provider's requirements. You can reference the same provider name in [`provider` blocks](/terraform/language/block/stack/configuration/provider) to further configure that provider.
+Each provider declaration uses the provider name as a key that maps to a block with the provider's requirements. You can reference the same provider name in [`provider` blocks](/terraform/language/block/stack/tfcomponent/provider) to further configure that provider.
 
 The following arguments are supported for each provider:
 

content/terraform/v1.13.x/docs/language/block/stack/component_configuration/removed.mdx renamed to content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/removed.mdx

@@ -177,7 +177,7 @@ You can only reference ephemeral variables from specific contexts or Terraform t
 - In an [`ephemeral` block](/terraform/language/block/ephemeral)
 - In the [`locals` block](/terraform/language/block/locals)
 - In other `variable` blocks with the `ephemeral` argument set to `true`
-- In [child module `output` blocks with the `ephemeral` argument set to `true`](/terraform/language/block/stack/configuration/output#ephemeral)
+- In [child module `output` blocks with the `ephemeral` argument set to `true`](/terraform/language/block/stack/tfcomponent/output#ephemeral)
 - Configuring [providers in the `provider` block](/terraform/language/functions/terraform-applying)
 - In [provisioner](/terraform/language/resources/provisioners/syntax) and [connection](/terraform/language/resources/provisioners/connection) blocks