[{"_1":2,"_300":-5,"_301":-5},"loaderData",{"_3":4,"_8":9,"_23":24},"root",{"_5":-5,"_6":7},"user","countable",true,"routes/_main",{"_5":-5,"_10":11},"recentPosts",[12,17,20],{"_13":14,"_15":16},"slug","claude-code-output-styles-explained","title","Claude Code Output Styles Explained, Including Concise",{"_13":18,"_15":19},"claude-code-skill-description-truncated","Why Claude Code Shortens or Drops Your Skill's Description",{"_13":21,"_15":22},"claude-code-skilloverrides-setting","Claude Code's skillOverrides Setting Explained","routes/creators.$handle",{"_25":26,"_27":26,"_28":29,"_30":31,"_32":33,"_298":31,"_299":99},"handle","hashicorp","displayName","profileUrl","https://github.com/hashicorp","verified",false,"skills",[34],{"_35":36,"_13":37,"_38":39,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_59":60,"_61":62,"_63":64,"_79":80,"_81":-5,"_82":83,"_84":85,"_86":87,"_88":89,"_90":91,"_92":-5,"_93":94,"_95":26,"_30":31,"_96":31,"_97":85,"_98":99,"_100":85,"_101":85,"_102":103,"_104":105,"_133":134,"_170":171,"_221":222,"_270":271,"_282":283,"_294":295,"_296":297},"id","gh__hashicorp__agent-skills__plugins-terraform-skills-terraform-stacks","terraform-stacks-hashicorp","name","Terraform Stacks","canonicalName","terraform-stacks","tagline","Streamline infrastructure management with Terraform.","description","Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, public registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.","longDescription","Terraform Stacks provide a structured approach to managing infrastructure as code, allowing developers and operations teams to orchestrate multiple components across various environments and regions seamlessly. By abstracting traditional Terraform modules into a stack configuration, users can define complete infrastructure units that can be deployed and modified together. This skill is particularly useful for teams managing complex cloud environments, as it simplifies the provisioning and management of resources across different stages of development.\n\nThe stack configuration utilizes a unique HCL-based language with specific file extensions for components and deployments, which enhances the clarity and organization of infrastructure code. Users can define components that encapsulate Terraform modules, specify input variables, and manage provider configurations through a straightforward syntax. This approach not only improves code readability but also facilitates better collaboration among team members, as the stack structure is easier to understand and maintain.\n\nAdditionally, Terraform Stacks support advanced features such as multi-region and multi-environment deployments, making them ideal for organizations that require robust infrastructure management across different cloud accounts. The skill also provides guidance on best practices for authentication, emphasizing the use of workload identity to enhance security and avoid the pitfalls of static credentials. Overall, Terraform Stacks empower teams to efficiently manage infrastructure at scale while adhering to best practices in security and code organization.","primaryCategory","development","subcategory","devops","secondaryCategories",[],"tags",[56,57,58,51,26],"terraform","infrastructure-as-code","cloud-management","skillType","reference","complexity","intermediate","platforms",[65,66,67,68,69,70,71,72,73,74,75,76,77,78],"claude-code","claude-api","codex-cli","cursor","antigravity","github-copilot","windsurf","opencode","cline","roo-code","goose","kiro","continue","trae","delivery","source-link","skillFileUrl","pricing","free","price",0,"thumbnailType","icon","thumbnailIcon","cloud","thumbnailColor","blue","thumbnailImageUrl","sellerId","gh__hashicorp","sellerName","featured","downloads","views",1,"rating","reviewCount","status","active","metrics",{"_106":107,"_108":99,"_109":110,"_111":107,"_112":85,"_113":114,"_115":116,"_117":118,"_119":120,"_121":122,"_123":124,"_125":126,"_127":128,"_129":130,"_131":132},"freshnessScore",100,"mirrorCount","skillCountInRepo",20,"qualityScore","daysSinceUpdate","popularityScore",60,"trustScore",55,"repoOpenIssues",25,"repoStars",792,"repoWatchers",13,"repoContributors",19,"overallScore",81,"repoCreatedAt","2025-11-08T02:07:20Z","repoForks",117,"repoPushedAt","2026-08-10T15:37:47Z","source",{"_135":26,"_136":137,"_138":139,"_144":145,"_146":147,"_148":-5,"_142":149,"_150":151,"_152":145,"_153":31,"_154":155,"_156":157,"_163":164,"_165":31,"_166":167,"_168":169},"owner","repoUrl","https://github.com/hashicorp/agent-skills","author",{"_28":29,"_140":141,"_38":26,"_25":26,"_142":143},"avatarUrl","https://github.com/hashicorp.png","type","User","lastSyncedAt","2026-08-11T01:33:14.798Z","repo","agent-skills","commitSha","github","branch","main","firstSeenAt","isOfficial","path","plugins/terraform/skills/terraform-stacks","license",{"_38":158,"_159":160,"_161":162},"GNU General Public License v3.0","spdxId","GPL-3.0","url","https://github.com/hashicorp/agent-skills/blob/main/LICENSE","sourceUpdatedAt","2026-08-10T15:37:46.000Z","redistributable","permalink","https://github.com/hashicorp/agent-skills/blob/main/plugins/terraform/skills/terraform-stacks/SKILL.md","repoFullName","hashicorp/agent-skills","seo",{"_172":173,"_184":185,"_186":187,"_205":-5,"_206":207,"_213":214,"_215":216,"_217":218,"_219":220},"useCases",[174,178,181],{"_15":175,"_176":177},"Multi-Environment Management","body","Use Terraform Stacks to manage infrastructure across development, staging, and production environments seamlessly.",{"_15":179,"_176":180},"Complex Cloud Deployments","Leverage Terraform Stacks to orchestrate resources across multiple cloud providers and regions for large-scale applications.",{"_15":182,"_176":183},"Team Collaboration on Infrastructure Code","Utilize the structured approach of Terraform Stacks to enhance collaboration and maintainability among team members working on infrastructure projects.","whenNotToUse","This skill may not be suitable for simple Terraform projects that do not require the orchestration of multiple components or environments.","faqs",[188,193,196,199,202],{"_189":190,"_191":192},"q","What are Terraform Stacks?","a","Terraform Stacks are a configuration layer that allows for the orchestration of multiple infrastructure components across different environments and regions, simplifying infrastructure management.",{"_189":194,"_191":195},"What file extensions are used with Terraform Stacks?","Terraform Stacks use specific file extensions such as .tfcomponent.hcl for component configurations and .tfdeploy.hcl for deployment configurations.",{"_189":197,"_191":198},"How do I manage provider configurations in Terraform Stacks?","Provider configurations in Terraform Stacks are defined within the .tfcomponent.hcl files, allowing for the specification of required providers and their settings.",{"_189":200,"_191":201},"What is the recommended way to handle authentication in Terraform Stacks?","The recommended approach is to use workload identity with OIDC tokens to avoid long-lived static credentials, enhancing security for your deployments.",{"_189":203,"_191":204},"Can I use local modules with Terraform Stacks?","Yes, Terraform Stacks support local modules, which can be referenced in the component definitions using local file paths.","ogImageUrl","keywords",[208,209,210,211,212],"terraform stacks","infrastructure management","hashicorp terraform","devops tooling","cloud provisioning","whenToUse","Use this skill when you need to create, modify, or validate Terraform Stack configurations for managing infrastructure at scale.","metaTitle","Terraform Stacks - Efficient Infrastructure Management","problemSolved","This skill simplifies the complexity of managing multiple infrastructure components and environments with Terraform.","metaDescription","Manage your infrastructure with Terraform Stacks for streamlined provisioning and deployment.","content",{"_223":224,"_225":226,"_252":253,"_263":264,"_265":31,"_266":267,"_268":269},"bundledFiles",6,"fileTree",[227,234,237,240,243,246,249],{"_154":228,"_229":230,"_142":231,"_232":233},"SKILL.md","size",17274,"file","language","markdown",{"_154":235,"_229":236,"_142":231,"_232":233},"references/api-monitoring.md",16608,{"_154":238,"_229":239,"_142":231,"_232":233},"references/component-blocks.md",10147,{"_154":241,"_229":242,"_142":231,"_232":233},"references/deployment-blocks.md",8863,{"_154":244,"_229":245,"_142":231,"_232":233},"references/examples.md",30727,{"_154":247,"_229":248,"_142":231,"_232":233},"references/linked-stacks.md",4341,{"_154":250,"_229":251,"_142":231,"_232":233},"references/troubleshooting.md",16711,"codeExamples",[254,258,261],{"_232":255,"_256":257},"text","snippet","my-stack/\n├── .terraform-version # The required Terraform version for this Stack\n├── variables.tfcomponent.hcl # Variable declarations\n├── providers.tfcomponent.hcl # Provider configurations\n├── components.tfcomponent.hcl # Component definitions\n├── outputs.tfcomponent.hcl # Stack outputs\n├── deployments.tfdeploy.hcl # Deployment definitions\n├── .terraform.lock.hcl # Provider lock file (generated)\n└── modules/ # Local modules (optional - only if using local modules)\n ├── s3/\n └── compute/",{"_232":259,"_256":260},"hcl","variable \"aws_region\" {\n type = string\n description = \"AWS region for deployments\"\n default = \"us-west-1\"\n}\n\nvariable \"identity_token\" {\n type = string\n description = \"OIDC identity token\"\n ephemeral = true # Does not persist to state file\n}\n\nvariable \"instance_count\" {\n type = number\n nullable = false\n}",{"_232":259,"_256":262},"required_providers {\n aws = {\n source = \"hashicorp/aws\"\n version = \"~> 6.0\"\n }\n random = {\n source = \"hashicorp/random\"\n version = \"~> 3.5.0\"\n }\n}","skillMd","# Terraform Stacks\n\nTerraform Stacks simplify infrastructure provisioning and management at scale by providing a configuration layer above traditional Terraform modules. Stacks enable declarative orchestration of multiple components across environments, regions, and cloud accounts.\n\n## Core Concepts\n\n**Stack**: A complete unit of infrastructure composed of components and deployments that can be managed together.\n\n**Component**: An abstraction around a Terraform module that defines infrastructure pieces. Each component specifies a source module, inputs, and providers.\n\n**Deployment**: An instance of all components in a stack with specific input values. Use deployments for different environments (dev/staging/prod), regions, or cloud accounts.\n\n**Stack Language**: A separate HCL-based language (not regular Terraform HCL) with distinct blocks and file extensions.\n\n## File Structure\n\nTerraform Stacks use specific file extensions:\n\n- **Component configuration**: `.tfcomponent.hcl`\n- **Deployment configuration**: `.tfdeploy.hcl`\n- **Provider lock file**: `.terraform.lock.hcl` (generated by CLI)\n\nAll configuration files must be at the root level of the Stack repository. HCP Terraform processes all files in dependency order.\n\n### Recommended File Organization\n\n```\nmy-stack/\n├── .terraform-version # The required Terraform version for this Stack\n├── variables.tfcomponent.hcl # Variable declarations\n├── providers.tfcomponent.hcl # Provider configurations\n├── components.tfcomponent.hcl # Component definitions\n├── outputs.tfcomponent.hcl # Stack outputs\n├── deployments.tfdeploy.hcl # Deployment definitions\n├── .terraform.lock.hcl # Provider lock file (generated)\n└── modules/ # Local modules (optional - only if using local modules)\n ├── s3/\n └── compute/\n```\n\n**Note**: The `modules/` directory is only required when using local module sources. Components can reference modules from:\n- Local file paths: `./modules/vpc`\n- Public registry: `terraform-aws-modules/vpc/aws`\n- Private registry: `app.terraform.io//vpc/aws`\n- Git: `git::https://github.com/org/repo.git//path?ref=v1.0.0`\n\nHCP Terraform processes all `.tfcomponent.hcl` and `.tfdeploy.hcl` files in dependency order.\n\n## Required Terraform version (.terraform-version)\n\nUse Terraform v1.13.x or later to access the Stacks CLI plugin and to run\nterraform stacks CLI commands. Begin by adding a .terraform-version file to\nyour Stack's root directory to specify the Terraform version required for your\nStack. For example, the following file specifies Terraform v1.14.5:\n\n```\n1.14.5\n```\n\n## Component Configuration (.tfcomponent.hcl)\n\n### Variable Block\n\nDeclare input variables for the Stack configuration. Variables must define a `type` field and do not support the `validation` argument.\n\n```hcl\nvariable \"aws_region\" {\n type = string\n description = \"AWS region for deployments\"\n default = \"us-west-1\"\n}\n\nvariable \"identity_token\" {\n type = string\n description = \"OIDC identity token\"\n ephemeral = true # Does not persist to state file\n}\n\nvariable \"instance_count\" {\n type = number\n nullable = false\n}\n```\n\n**Important**: Use `ephemeral = true` for credentials and tokens (identity tokens, API keys, passwords) to prevent them from persisting in state files. Use `stable` for longer-lived values like license keys that need to persist across runs.\n\n### Required Providers Block\n\n```hcl\nrequired_providers {\n aws = {\n source = \"hashicorp/aws\"\n version = \"~> 6.0\"\n }\n random = {\n source = \"hashicorp/random\"\n version = \"~> 3.5.0\"\n }\n}\n```\n\n### Provider Block\n\nProvider blocks differ from traditional Terraform:\n\n1. Support `for_each` meta-argument\n2. Define aliases in the block header (not as an argument)\n3. Accept configuration through a `config` block\n\n**Single Provider Configuration:**\n\n```hcl\nprovider \"aws\" \"this\" {\n config {\n region = var.aws_region\n assume_role_with_web_identity {\n role_arn = var.role_arn\n web_identity_token = var.identity_token\n }\n }\n}\n```\n\n**Multiple Provider Configurations with for_each:**\n\n```hcl\nprovider \"aws\" \"configurations\" {\n for_each = var.regions\n\n config {\n region = each.value\n assume_role_with_web_identity {\n role_arn = var.role_arn\n web_identity_token = var.identity_token\n }\n }\n}\n```\n\n**Authentication Best Practice**: Use **workload identity** (OIDC) as the preferred authentication method for Stacks. This approach:\n- Avoids long-lived static credentials\n- Provides temporary, scoped credentials per deployment run\n- Integrates with cloud provider IAM (AWS IAM Roles, Azure Managed Identities, GCP Service Accounts)\n- Eliminates need for platform-managed environment variables\n\nConfigure workload identity using `identity_token` blocks and `assume_role_with_web_identity` in provider configuration. For detailed setup instructions for AWS, Azure, and GCP, see: https://developer.hashicorp.com/terraform/cloud-docs/dynamic-provider-credentials\n\n### Component Block\n\nEach Stack requires at least one component block. Add a component for each module to include in the Stack. Components reference modules from local paths, registries, or Git.\n\n```hcl\ncomponent \"vpc\" {\n source = \"app.terraform.io/my-org/vpc/aws\" # Local, registry, or Git URL\n version = \"2.1.0\" # For registry modules\n\n inputs = {\n cidr_block = var.vpc_cidr\n name_prefix = var.name_prefix\n }\n\n providers = {\n aws = provider.aws.this\n }\n}\n```\n\nSee `references/component-blocks.md` for examples of dependencies, for_each, public registry modules, Git sources, and more.\n\n**Key Points:**\n- Reference outputs: `component..` or `component.[key].` for for_each\n- Dependencies inferred automatically from component references\n- Aggregate with for expressions: `[for x in component.s3 : x.bucket_name]`\n- For components with `for_each`, reference specific instances: `component.[each.value].`\n- Provider references are normal values: `provider..` or `provider..[each.value]`\n\n### Output Block\n\nOutputs require a `type` argument and do not support `preconditions`:\n\n```hcl\noutput \"vpc_id\" {\n type = string\n description = \"VPC ID\"\n value = component.vpc.vpc_id\n}\n\noutput \"endpoint_urls\" {\n type = map(string)\n value = {\n for region, comp in component.api : region => comp.endpoint_url\n }\n sensitive = false\n}\n```\n\n### Locals Block\n\nLocals blocks work the same in both `.tfcomponent.hcl` and `.tfdeploy.hcl` files:\n\n```hcl\nlocals {\n common_tags = {\n Environment = var.environment\n ManagedBy = \"Terraform Stacks\"\n Project = var.project_name\n }\n\n region_config = {\n for region in var.regions : region => {\n name_suffix = \"${var.environment}-${region}\"\n }\n }\n}\n```\n\n### Removed Block\n\nUse to safely remove components from a Stack. HCP Terraform requires the component's providers to remove it.\n\n```hcl\nremoved {\n from = component.old_component\n source = \"./modules/old-module\"\n\n providers = {\n aws = provider.aws.this\n }\n}\n```\n\n## Deployment Configuration (.tfdeploy.hcl)\n\n### Identity Token Block\n\nGenerate JWT tokens for OIDC authentication with cloud providers:\n\n```hcl\nidentity_token \"aws\" {\n audience = [\"aws.workload.identity\"]\n}\n\nidentity_token \"azure\" {\n audience = [\"api://AzureADTokenExchange\"]\n}\n```\n\nReference tokens in deployments using `identity_token..jwt`\n\n### Store Block\n\nAccess HCP Terraform variable sets within Stack deployments:\n\n```hcl\nstore \"varset\" \"aws_credentials\" {\n id = \"varset-ABC123\" # Alternatively use: name = \"varset_name\"\n source = \"tfc-cloud-shared\"\n category = \"terraform\" # Alternatively use: category = \"env\" for environment variables\n}\n\ndeployment \"production\" {\n inputs = {\n aws_access_key = store.varset.aws_credentials.AWS_ACCESS_KEY_ID\n }\n}\n```\n\nUse to centralize credentials and share variables across Stacks. See `references/deployment-blocks.md` for details.\n\n### Deployment Block\n\nDefine deployment instances (minimum 1, maximum 20 per Stack):\n\n```hcl\ndeployment \"production\" {\n inputs = {\n aws_region = \"us-west-1\"\n instance_count = 3\n role_arn = local.role_arn\n identity_token = identity_token.aws.jwt\n }\n}\n\n# Create multiple deployments for different environments\ndeployment \"development\" {\n inputs = {\n aws_region = \"us-east-1\"\n instance_count = 1\n name_suffix = \"dev\"\n role_arn = local.role_arn\n identity_token = identity_token.aws.jwt\n }\n}\n```\n\n**To destroy a deployment**: Set `destroy = true`, upload configuration, approve destroy run, then remove the deployment block. See `references/deployment-blocks.md` for details.\n\n### Deployment Group Block\n\nGroup deployments together for shared settings (HCP Terraform Premium tier feature). Free/standard tiers use default groups named `{deployment-name}_default`.\n\n```hcl\ndeployment_group \"canary\" {\n auto_approve_checks = [deployment_auto_approve.safe_changes]\n}\n\ndeployment \"dev\" {\n inputs = { /* ... */ }\n deployment_group = deployment_group.canary\n}\n```\n\nMultiple deployments can reference the same group. See `references/deployment-blocks.md` for details.\n\n### Deployment Auto-Approve Block\n\nDefine rules to automatically approve deployment plans (HCP Terraform Premium tier feature):\n\n```hcl\ndeployment_auto_approve \"safe_changes\" {\n deployment_group = deployment_group.canary\n\n check {\n condition = context.plan.changes.remove == 0\n reason = \"Cannot auto-approve plans with resource deletions\"\n }\n}\n```\n\n**Available context variables**: `context.plan.applyable`, `context.plan.changes.add/change/remove/total`, `context.success`\n\n**Note:** `orchestrate` blocks are deprecated. Use `deployment_group` and `deployment_auto_approve` instead.\n\nSee `references/deployment-blocks.md` for all context variables and patterns.\n\n### Publish Output and Upstream Input Blocks\n\nLink Stacks together by publishing outputs from one Stack and consuming them in another:\n\n```hcl\n# In network Stack - publish outputs\npublish_output \"vpc_id_network\" {\n type = string\n value = deployment.network.vpc_id\n}\n\n# In application Stack - consume outputs\nupstream_input \"network_stack\" {\n type = \"stack\"\n source = \"app.terraform.io/my-org/my-project/networking-stack\"\n}\n\ndeployment \"app\" {\n inputs = {\n vpc_id = upstream_input.network_stack.vpc_id_network\n }\n}\n```\n\nSee `references/linked-stacks.md` for complete documentation and examples.\n\n## Terraform Stacks CLI\n\n**Note**: Terraform Stacks is Generally Available (GA) as of Terraform CLI v1.13+. Stacks now count toward Resources Under Management (RUM) for HCP Terraform billing.\n\n### Initialize and Validate\n\n```bash\nterraform stacks init # Download providers, modules, generate lock file\nterraform stacks providers-lock # Regenerate lock file (add platforms if needed)\nterraform stacks validate # Check syntax without uploading\n```\n\n### Deployment Workflow\n\n**Important**: No `plan` or `apply` commands. Upload configuration triggers deployment runs automatically.\n\n```bash\n# 1. Upload configuration (triggers deployment runs)\nterraform stacks configuration upload\n\n# 2. Monitor deployments\nterraform stacks deployment-run list # List runs (non-interactive)\nterraform stacks deployment-group watch -deployment-group=... # Stream status updates\n\n# 3. Approve deployments (if auto-approve not configured)\nterraform stacks deployment-run approve-all-plans -deployment-run-id=...\nterraform stacks deployment-group approve-all-plans -deployment-group=...\nterraform stacks deployment-run cancel -deployment-run-id=... # Cancel if needed\n```\n\n### Configuration Management\n\n```bash\nterraform stacks configuration list # List configuration versions\nterraform stacks configuration fetch -configuration-id=... # Download configuration\nterraform stacks configuration watch # Monitor upload status\n```\n\n### Other Commands\n\n```bash\nterraform stacks create # Create new Stack (interactive)\nterraform stacks fmt # Format Stack files\nterraform stacks list # Show all Stacks\nterraform stacks version # Display version\nterraform stacks deployment-group rerun -deployment-group=... # Rerun deployment\n```\n\n## Monitoring Deployments with HCP Terraform API\n\nFor programmatic monitoring in automation, CI/CD, or non-interactive environments (like AI agents), use the HCP Terraform API instead of CLI watch commands. The API provides endpoints for:\n\n- Configuration status and validation\n- Deployment group summaries\n- Deployment run status\n- Deployment step details (plan/apply)\n- Error diagnostics with file locations and code snippets\n- Stack outputs via artifacts endpoint\n\n**Key points:**\n- CLI watch commands stream indefinitely and don't work in automation\n- Use artifacts endpoint to retrieve Stack outputs: `GET /api/v2/stack-deployment-steps/{step-id}/artifacts?name=apply-description`\n- Diagnostics endpoint requires `stack_deployment_step_id` query parameter\n- Artifacts endpoint returns HTTP 307 redirect (use `curl -L`)\n\nFor complete API workflow, authentication, polling best practices, and example scripts, see `references/api-monitoring.md`.\n\n## Common Patterns\n\n**Component Dependencies**: Dependencies are automatically inferred when one component references another's output (e.g., `subnet_ids = component.vpc.private_subnet_ids`).\n\n**Multi-Region Deployment**: Use `for_each` on providers and components to deploy across multiple regions. Each region gets its own provider configuration and component instances.\n\n**Deferred Changes**: Stacks support deferred changes to handle dependencies where values are only known after apply. This enables complex multi-component deployments where some resources depend on runtime values from other components (cluster endpoints, generated passwords, etc.).\n\nFor complete examples including multi-region deployments, component dependencies, deferred changes patterns, and linked Stacks, see `references/examples.md`.\n\n## Best Practices\n\n1. **Component Granularity**: Create components for logical infrastructure units that share a lifecycle\n2. **Module Compatibility**:\n - Modules used with Stacks cannot include provider blocks (configure providers in Stack configuration)\n - **Test public registry modules** before using in production Stacks - some modules may have compatibility issues\n - Consider using raw resources for critical infrastructure if module compatibility is uncertain\n - Example: Some terraform-aws-modules versions have been found to have compatibility issues with Stacks (e.g., ALB and ECS modules)\n3. **State Isolation**: Each deployment has its own isolated state\n4. **Input Variables**: Use variables for values that differ across deployments; use locals for shared values\n5. **Provider Lock Files**: Always generate and commit `.terraform.lock.hcl` to version control\n6. **Naming Conventions**: Use descriptive names for components and deployments\n7. **Deployment Groups**: You can organize deployments into deployment groups. Deployment groups enable auto-approval rules, logical organization, and provide a foundation for scaling. Deployment groups are an HCP Terraform Premium tier feature\n8. **Testing**: Test Stack configurations in dev/staging deployments before production\n\n## Troubleshooting\n\n**Circular Dependencies**: Refactor to break circular references or use intermediate components.\n\n**Deployment Destruction**: Cannot destroy from UI. Set `destroy = true` in deployment block, upload configuration, and HCP Terraform creates a destroy run.\n\n**Empty Diagnostics**: Add required `stack_deployment_step_id` query parameter to diagnostics API requests.\n\n**Module Compatibility**: Test public registry modules before production use. Some modules may have compatibility issues with Stacks.\n\n## References\n\nFor detailed documentation, see:\n- `references/component-blocks.md` - Complete component block reference with all arguments and syntax\n- `references/deployment-blocks.md` - Complete deployment block reference with all configuration options\n- `references/linked-stacks.md` - Publish outputs and upstream inputs for linking Stacks together\n- `references/examples.md` - Complete working examples for multi-region and component dependencies\n- `references/api-monitoring.md` - Full API workflow for programmatic monitoring and automation\n- `references/troubleshooting.md` - Detailed troubleshooting guide for common issues and solutions","skillMdTruncated","frontmatter",{"_38":41,"_44":45},"totalSizeBytes",104671,"runtime",{"_272":7,"_273":31,"_274":-5,"_275":31,"_276":7,"_277":31,"_278":279,"_280":281},"requiresBash","requiresMcp","model","requiresNode","requiresNetwork","requiresPython","allowedTools",[],"dependencies",[],"install",{"_284":285,"_286":287,"_288":289,"_290":291,"_292":293},"cli","npx skills add hashicorp/agent-skills/terraform-stacks","coordinate","hashicorp/agent-skills/terraform-stacks","browseUrl","https://github.com/hashicorp/agent-skills/tree/main/plugins/terraform/skills/terraform-stacks","downloadUrl","https://github.com/hashicorp/agent-skills/archive/refs/heads/main.zip","gitUrl","https://github.com/hashicorp/agent-skills.git","createdAt","2026-08-11T01:33:20.105Z","updatedAt","2026-08-12T01:15:28.187Z","hasNext","page","actionData","errors"]