Add import

Author: rkoron007

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

@@ -153,30 +153,31 @@ We recommend using the `destroy` argument to remove deployments to ensure your c
 - Data type: Boolean
 - Default: `false`
 
-### `import`
+<!-- TODO: Clear this up when we have the migrate docs -->
 
-The `import` argument lets you declare in configuration that the deployment can import existing infrastructure into its state before deploying.
+### `import`
 
+The `tf-migrate` CLI can migrate the state of an existing HCP Terraform workspace to a Stack deployment. The `tf-migrate` CLI automatically sets the `import` argument to `true` when importing the state of an existing workspace to a specific deployment.
 
 ```hcl
 deployment "<LABEL>" {
   inputs = {
     <VARIABLE_NAME> = <VALUE>
     <VARIABLE_NAME_TWO> = <VALUE_TWO>
   }
-  import = true
+  import = <boolean>
 }
 ```
 
-The `tf-migrate` tool automatically sets the `import` argument to `true` when importing the state of an HCP Ter.
+Terraform migrate sets the `import` argument to let HCP Terraform know that the rest of the deployments in a Stack can continue plan as normal while the deployment with `import` is migrating state.
+
+To learn more about migrating a workspace to a Stack deployment, refer to Terraform migrate](/terraform/migrate).
 
 #### Summary
 
 - Data type: Boolean
 - Default: `false`
 
-
-
 ## Examples
 
 The following examples demonstrate common use cases for `deployment` blocks.

content/terraform/v1.13.x/docs/language/stacks/component/manage.mdx

@@ -0,0 +1,114 @@
+---
+page_title: Manage components and resources in Stacks
+description: |-
+  Learn how to update your Stack component configuration to manage components. Also, learn how to manage resources within the Terraform modules that each component sources.
+---
+
+# Manage components and resources in Stacks
+
+Stacks are made up of components, and each component includes a Terraform module as its source. Learn how to add and remove components from a Stack, and how to manage resources within the module that each component sources.
+
+## Add components
+
+The `component` block defines the pieces that make up your Stack. Add a `component` block for each top-level module you want to include in the Stack. You must specify the source module, inputs, and providers for each component. To learn more about the `component` refer to the [`component` block reference](/terraform/language/block/stack/component_configuration/component).
+
+## Remove components
+
+Stacks take a systematic approach to removing components from your configuration. You must use a dedicated `removed` block in your component configuration to ensure Terraform can properly remove your component and the resources associated with that component.
+
+To remove a component, add a `removed` block to your component configuration specifying the component you want to remove. For example, if you want to remove the following `database` component:
+
+<CodeBlockConfig filename="component.tfcomponent.hcl">
+
+```hcl
+component "database" {
+  source = "./modules/database"
+
+  inputs = {
+    instance_class = "db.t3.micro"
+  }
+
+  providers = {
+    aws = provider.aws.main
+  }
+}
+```
+</CodeBlockConfig>
+
+You add a `removed` block that specifies the component to remove, module that component sources, and the providers that component uses. The `removed` block also tells Terraform to destroy the resources managed by a component.
+
+<TIP>
+
+Do not remove providers from your component configuration without first removing the components that require those providers. Terraform requires a component's providers to ensure it can successfully remove that component.
+
+</TIP>
+
+In the following example, Terraform removes the `database` component that sources from `./modules/database` and uses the `aws.main` provider:
+
+```hcl
+component "database" {
+  source = "./modules/database"
+
+  inputs = {
+    instance_class = "db.t3.micro"
+  }
+
+  providers = {
+    aws = provider.aws.main
+  }
+}
+
+removed {
+  source = "./modules/database"
+  from   = component.database
+
+  providers = {
+    aws = provider.aws.main
+  }
+}
+```
+
+After you apply the configuration in HCP Terraform, Terraform removes the `database` component and its resources from the associated Stack deployments. You can then remove both the `component` block and the `removed` block from your component configuration file.
+
+If your `component` block uses the `for_each` meta-argument to define multiple components, you can define a `removed` block with the `for_each` meta-argument to ensure Terraform destroys each component instance.
+
+In the following example, the `removed` block iterates through `local.deprecated_components` to remove the `staging` components and corresponding resources:
+
+```hcl
+locals {
+  components = ["dev", "prod"]
+  deprecated_components = ["staging"]
+}
+
+component "env" {
+  for_each = toset(local.components)
+
+  source = "../local-component"
+
+  providers = {
+    #...
+  }
+  #...
+}
+
+removed {
+  for_each = toset(local.deprecated_components)
+  from = component.env[each.key]
+
+  providers = {
+    #...
+  }
+}
+```
+
+In the above example, you can delete a component by removing it from the `local.components` list and adding it to the `local.removed_components` list.
+
+## Manage resources
+
+A Stack component sources its configuration from a module. Module use traditional Terraform configuration files that end with `.tf`. To interact with individual resources in a component, you must update the module your component sources its configuration from.
+
+Use the following blocks in the Terraform configuration files that make up your module to manage individual resources:
+
+- To remove a resource from your module, use the `removed` block. To learn more, refer to [Destroy a resource](/terraform/language/resources/destroy).
+- To tell Terraform to take over the management of an existing infrastructure resource, use the `import` block. To learn more, refer to [Import a resource](/terraform/language/import).
+- To move a resource from one module to another, use the `moved` block. To learn more, refer to [Move a resource](/terraform/language/modules/develop/refactoring#move-a-resource-or-module).

content/terraform/v1.13.x/docs/language/stacks/deploy/conditions.mdx

@@ -24,7 +24,6 @@ Add the `deployment_group` block to your deployment configuration to create a ne
 <CodeBlockConfig filename="deployments.tfdeploy.hcl">
 
 ```hcl
-
 deployment_group "staging_group" {
    # ...
 }