---
title: "Terraform Stacks: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/hashicorp-terraform-stacks/
description: "Covers Terraform Stacks component and deployment files, including the required Terraform version file."
---

# Terraform Stacks: review, setup & limitations · Undominated.ai

> Covers Terraform Stacks component and deployment files, including the required Terraform version file.

[← Explore all skills](/skills/)

INFRASTRUCTURE DEVELOPMENT / HashiCorp

# Terraform Stacks

Covers Terraform Stacks component and deployment files, including the required Terraform version file.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/hashicorp/agent-skills/tree/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher HashiCorp
 Licence [MPL-2.0 ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE)
 Revision f706481af9b8
 [Read what was—and wasn’t—checked ↓](#review)

“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.”

 [HashiCorp · upstream description ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The definition names .tfcomponent.hcl and .tfdeploy.hcl as distinct files.
- A heading requires a .terraform-version file rather than assuming the latest CLI.

### A good fit for

 - Writing a Stack component
- Checking a multi-environment deployment file
- Model per-environment deployments from shared component modules.
- Separate local Stack syntax validation from uploads that trigger deployment runs.

### Weigh up before choosing

 - MPL-2.0 applies to modified redistributions of this file.
- Stacks examples are not a plan against your cloud account.
- Stack HCL is a separate language: ordinary Terraform variable validation/provider-block assumptions do not transfer unchanged.
- Configuration upload triggers deployment runs according to the pinned source; it is not a local syntax-only check.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/terraform/skills/terraform-stacks/SKILL.md
- README.md
- LICENSE
- vercel-labs/skills@48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e:README.md
- SKILLS.md

### Our findings

 - Headings separate component configuration from deployment configuration.
- The description names local, public-registry and private-registry component sources.
- Definition separates .tfcomponent.hcl from .tfdeploy.hcl and explains deferred component changes.
- Deployment-level state isolation and explicit ephemeral credentials are part of the model, not proof that source examples match a live account.
- Variables must declare type and do not support validation. Outputs require type and do not support preconditions.
- The Stacks CLI workflow separates syntax validation from configuration upload, and explicitly states that uploading starts deployment runs.

### Not established by this review

 - The skill was not executed inside a host agent.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/48dc9e8eb8aa19040e91cb90ba0b642c9cbad57e/README.md)

DOCUMENTED COMMAND

 npx skills add hashicorp/agent-skills/plugins/terraform/skills/terraform-stacks --skill terraform-stacks Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills@1.7.1 add https://github.com/hashicorp/agent-skills/tree/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks --skill terraform-stacks Copy reviewed-revision command ↗ - The command pins the reviewed tree and Skills CLI 1.7.1 (vercel-labs/skills package.json at 48dc9e8e). The publisher documents npx skills add hashicorp/agent-skills/<installation-path> in SKILLS.md, which follows the default branch.
- Retain all supporting files; separately configure companion skills, runtimes and service credentials named in the definition.
- Review the resulting diff and use an isolated target before any migration, deployment, load test or warehouse operation.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/hashicorp-terraform-stacks/bundle.zip and extract it into a new directory. It holds SKILL.md and 6 supporting files unchanged at revision f706481a, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named terraform-stacks. Keep SKILL.md and the licence together.

### Before you start

 - Terraform v1.13 or later for the Stacks CLI (the file's example pins 1.14.5), an HCP Terraform organization and a scoped workload identity. Deployment groups and auto-approve rules are an HCP Terraform Premium tier feature.

### Compatibility

Agent Skills-compatible hosts · Terraform Stacks

### Local Markdown instructions

 - Read the installed skill files
- Stack uploads and approval rules can trigger real plans, applies or destroy runs across accounts.

### Cost model

Source is free to read under the stated licence. A host agent may charge for use.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download complete resource + licence ↗](/resources/skills/hashicorp-terraform-stacks/bundle.zip)[Raw Markdown ↗](/resources/skills/hashicorp-terraform-stacks/definition.md)
 ---
name: terraform-stacks
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.
metadata:
 lifecycle-status: active
 copyright: Copyright IBM Corp. 2026
 version: "0.0.1"
---

# Terraform Stacks

Terraform 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.

## Core Concepts

**Stack**: A complete unit of infrastructure composed of components and deployments that can be managed together.

**Component**: An abstraction around a Terraform module that defines infrastructure pieces. Each component specifies a source module, inputs, and providers.

**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.

**Stack Language**: A separate HCL-based language (not regular Terraform HCL) with distinct blocks and file extensions.

## File Structure

Terraform Stacks use specific file extensions:

- **Component configuration**: `.tfcomponent.hcl`
- **Deployment configuration**: `.tfdeploy.hcl`
- **Provider lock file**: `.terraform.lock.hcl` (generated by CLI)

All configuration files must be at the root level of the Stack repository. HCP Terraform processes all files in dependency order.

### Recommended File Organization

```
my-stack/
├── .terraform-version # The required Terraform version for this Stack
├── variables.tfcomponent.hcl # Variable declarations
├── providers.tfcomponent.hcl # Provider configurations
├── components.tfcomponent.hcl # Component definitions
├── outputs.tfcomponent.hcl # Stack outputs
├── deployments.tfdeploy.hcl # Deployment definitions
├── .terraform.lock.hcl # Provider lock file (generated)
└── modules/ # Local modules (optional - only if using local modules)
 ├── s3/
 └── compute/
```

**Note**: The `modules/` directory is only required when using local module sources. Components can reference modules from:
- Local file paths: `./modules/vpc`
- Public registry: `terraform-aws-modules/vpc/aws`
- Private registry: `app.terraform.io/<org-name>/vpc/aws`
- Git: `git::https://github.com/org/repo.git//path?ref=v1.0.0`

HCP Terraform processes all `.tfcomponent.hcl` and `.tfdeploy.hcl` files in dependency order.

## Required Terraform version (.terraform-version)

Use Terraform v1.13.x or later to access the Stacks CLI plugin and to run
terraform stacks CLI commands. Begin by adding a .terraform-version file to
your Stack's root directory to specify the Terraform version required for your
Stack. For example, the following file specifies Terraform v1.14.5:

```
1.14.5
```

## Component Configuration (.tfcomponent.hcl)

### Variable Block

Declare input variables for the Stack configuration. Variables must define a `type` field and do not support the `validation` argument.

```hcl
variable "aws_region" {
 type = string
 description = "AWS region for deployments"
 default = "us-west-1"
}

variable "identity_token" {
 type = string
 description = "OIDC identity token"
 ephemeral = true # Does not persist to state file
}

variable "instance_count" {
 type = number
 nullable = false
}
```

**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.

### Required Providers Block

```hcl
required_providers {
 aws = {
 source = "hashicorp/aws"
 version = "~> 6.0"
 }
 random = {
 source = "hashicorp/random"
 version = "~> 3.5.0"
 }
}
```

### Provider Block

Provider blocks differ from traditional Terraform:

1. Support `for_each` meta-argument
2. Define aliases in the block header (not as an argument)
3. Accept configuration through a `config` block

**Single Provider Configuration:**

```hcl
provider "aws" "this" {
 config {
 region = var.aws_region
 assume_role_with_web_identity {
 role_arn = var.role_arn
 web_identity_token = var.identity_token
 }
 }
}
```

**Multiple Provider Configurations with for_each:**

```hcl
provider "aws" "configurations" {
 for_each = var.regions

 config {
 region = each.value
 assume_role_with_web_identity {
 role_arn = var.role_arn
 web_identity_token = var.identity_token
 }
 }
}
```

**Authentication Best Practice**: Use **workload identity** (OIDC) as the preferred authentication method for Stacks. This approach:
- Avoids long-lived static credentials
- Provides temporary, scoped credentials per deployment run
- Integrates with cloud provider IAM (AWS IAM Roles, Azure Managed Identities, GCP Service Accounts)
- Eliminates need for platform-managed environment variables

Configure 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

### Component Block

Each 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.

```hcl
component "vpc" {
 source = "app.terraform.io/my-org/vpc/aws" # Local, registry, or Git URL
 version = "2.1.0" # For registry modules

 inputs = {
 cidr_block = var.vpc_cidr
 name_prefix = var.name_prefix
 }

 providers = {
 aws = provider.aws.this
 }
}
```

See `references/component-blocks.md` for examples of dependencies, for_each, public registry modules, Git sources, and more.

**Key Points:**
- Reference outputs: `component.<name>.<output>` or `component.<name>[key].<output>` for for_each
- Dependencies inferred automatically from component references
- Aggregate with for expressions: `[for x in component.s3 : x.bucket_name]`
- For components with `for_each`, reference specific instances: `component.<name>[each.value].<output>`
- Provider references are normal values: `provider.<type>.<alias>` or `provider.<type>.<alias>[each.value]`

### Output Block

Outputs require a `type` argument and do not support `preconditions`:

```hcl
output "vpc_id" {
 type = string
 description = "VPC ID"
 value = component.vpc.vpc_id
}

output "endpoint_urls" {
 type = map(string)
 value = {
 for region, comp in component.api : region => comp.endpoint_url
 }
 sensitive = false
}
```

### Locals Block

Locals blocks work the same in both `.tfcomponent.hcl` and `.tfdeploy.hcl` files:

```hcl
locals {
 common_tags = {
 Environment = var.environment
 ManagedBy = "Terraform Stacks"
 Project = var.project_name
 }

 region_config = {
 for region in var.regions : region => {
 name_suffix = "${var.environment}-${region}"
 }
 }
}
```

### Removed Block

Use to safely remove components from a Stack. HCP Terraform requires the component's providers to remove it.

```hcl
removed {
 from = component.old_component
 source = "./modules/old-module"

 providers = {
 aws = provider.aws.this
 }
}
```

## Deployment Configuration (.tfdeploy.hcl)

### Identity Token Block

Generate JWT tokens for OIDC authentication with cloud providers:

```hcl
identity_token "aws" {
 audience = ["aws.workload.identity"]
}

identity_token "azure" {
 audience = ["api://AzureADTokenExchange"]
}
```

Reference tokens in deployments using `identity_token.<name>.jwt`

### Store Block

Access HCP Terraform variable sets within Stack deployments:

```hcl
store "varset" "aws_credentials" {
 id = "varset-ABC123" # Alternatively use: name = "varset_name"
 source = "tfc-cloud-shared"
 category = "terraform" # Alternatively use: category = "env" for environment variables
}

deployment "production" {
 inputs = {
 aws_access_key = store.varset.aws_credentials.AWS_ACCESS_KEY_ID
 }
}
```

Use to centralize credentials and share variables across Stacks. See `references/deployment-blocks.md` for details.

### Deployment Block

Define deployment instances (minimum 1, maximum 20 per Stack):

```hcl
deployment "production" {
 inputs = {
 aws_region = "us-west-1"
 instance_count = 3
 role_arn = local.role_arn
 identity_token = identity_token.aws.jwt
 }
}

# Create multiple deployments for different environments
deployment "development" {
 inputs = {
 aws_region = "us-east-1"
 instance_count = 1
 name_suffix = "dev"
 role_arn = local.role_arn
 identity_token = identity_token.aws.jwt
 }
}
```

**To destroy a deployment**: Set `destroy = true`, upload configuration, approve destroy run, then remove the deployment block. See `references/deployment-blocks.md` for details.

### Deployment Group Block

Group deployments together for shared settings (HCP Terraform Premium tier feature). Free/standard tiers use default groups named `{deployment-name}_default`.

```hcl
deployment_group "canary" {
 auto_approve_checks = [deployment_auto_approve.safe_changes]
}

deployment "dev" {
 inputs = { /* ... */ }
 deployment_group = deployment_group.canary
}
```

Multiple deployments can reference the same group. See `references/deployment-blocks.md` for details.

### Deployment Auto-Approve Block

Define rules to automatically approve deployment plans (HCP Terraform Premium tier feature):

```hcl
deployment_auto_approve "safe_changes" {
 deployment_group = deployment_group.canary

 check {
 condition = context.plan.changes.remove == 0
 reason = "Cannot auto-approve plans with resource deletions"
 }
}
```

**Available context variables**: `context.plan.applyable`, `context.plan.changes.add/change/remove/total`, `context.success`

**Note:** `orchestrate` blocks are deprecated. Use `deployment_group` and `deployment_auto_approve` instead.

See `references/deployment-blocks.md` for all context variables and patterns.

### Publish Output and Upstream Input Blocks

Link Stacks together by publishing outputs from one Stack and consuming them in another:

```hcl
# In network Stack - publish outputs
publish_output "vpc_id_network" {
 type = string
 value = deployment.network.vpc_id
}

# In application Stack - consume outputs
upstream_input "network_stack" {
 type = "stack"
 source = "app.terraform.io/my-org/my-project/networking-stack"
}

deployment "app" {
 inputs = {
 vpc_id = upstream_input.network_stack.vpc_id_network
 }
}
```

See `references/linked-stacks.md` for complete documentation and examples.

## Terraform Stacks CLI

**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.

### Initialize and Validate

```bash
terraform stacks init # Download providers, modules, generate lock file
terraform stacks providers-lock # Regenerate lock file (add platforms if needed)
terraform stacks validate # Check syntax without uploading
```

### Deployment Workflow

**Important**: No `plan` or `apply` commands. Upload configuration triggers deployment runs automatically.

```bash
# 1. Upload configuration (triggers deployment runs)
terraform stacks configuration upload

# 2. Monitor deployments
terraform stacks deployment-run list # List runs (non-interactive)
terraform stacks deployment-group watch -deployment-group=... # Stream status updates

# 3. Approve deployments (if auto-approve not configured)
terraform stacks deployment-run approve-all-plans -deployment-run-id=...
terraform stacks deployment-group approve-all-plans -deployment-group=...
terraform stacks deployment-run cancel -deployment-run-id=... # Cancel if needed
```

### Configuration Management

```bash
terraform stacks configuration list # List configuration versions
terraform stacks configuration fetch -configuration-id=... # Download configuration
terraform stacks configuration watch # Monitor upload status
```

### Other Commands

```bash
terraform stacks create # Create new Stack (interactive)
terraform stacks fmt # Format Stack files
terraform stacks list # Show all Stacks
terraform stacks version # Display version
terraform stacks deployment-group rerun -deployment-group=... # Rerun deployment
```

## Monitoring Deployments with HCP Terraform API

For 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:

- Configuration status and validation
- Deployment group summaries
- Deployment run status
- Deployment step details (plan/apply)
- Error diagnostics with file locations and code snippets
- Stack outputs via artifacts endpoint

**Key points:**
- CLI watch commands stream indefinitely and don't work in automation
- Use artifacts endpoint to retrieve Stack outputs: `GET /api/v2/stack-deployment-steps/{step-id}/artifacts?name=apply-description`
- Diagnostics endpoint requires `stack_deployment_step_id` query parameter
- Artifacts endpoint returns HTTP 307 redirect (use `curl -L`)

For complete API workflow, authentication, polling best practices, and example scripts, see `references/api-monitoring.md`.

## Common Patterns

**Component Dependencies**: Dependencies are automatically inferred when one component references another's output (e.g., `subnet_ids = component.vpc.private_subnet_ids`).

**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.

**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.).

For complete examples including multi-region deployments, component dependencies, deferred changes patterns, and linked Stacks, see `references/examples.md`.

## Best Practices

1. **Component Granularity**: Create components for logical infrastructure units that share a lifecycle
2. **Module Compatibility**:
 - Modules used with Stacks cannot include provider blocks (configure providers in Stack configuration)
 - **Test public registry modules** before using in production Stacks - some modules may have compatibility issues
 - Consider using raw resources for critical infrastructure if module compatibility is uncertain
 - Example: Some terraform-aws-modules versions have been found to have compatibility issues with Stacks (e.g., ALB and ECS modules)
3. **State Isolation**: Each deployment has its own isolated state
4. **Input Variables**: Use variables for values that differ across deployments; use locals for shared values
5. **Provider Lock Files**: Always generate and commit `.terraform.lock.hcl` to version control
6. **Naming Conventions**: Use descriptive names for components and deployments
7. **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
8. **Testing**: Test Stack configurations in dev/staging deployments before production

## Troubleshooting

**Circular Dependencies**: Refactor to break circular references or use intermediate components.

**Deployment Destruction**: Cannot destroy from UI. Set `destroy = true` in deployment block, upload configuration, and HCP Terraform creates a destroy run.

**Empty Diagnostics**: Add required `stack_deployment_step_id` query parameter to diagnostics API requests.

**Module Compatibility**: Test public registry modules before production use. Some modules may have compatibility issues with Stacks.

## References

For detailed documentation, see:
- `references/component-blocks.md` - Complete component block reference with all arguments and syntax
- `references/deployment-blocks.md` - Complete deployment block reference with all configuration options
- `references/linked-stacks.md` - Publish outputs and upstream inputs for linking Stacks together
- `references/examples.md` - Complete working examples for multi-region and component dependencies
- `references/api-monitoring.md` - Full API workflow for programmatic monitoring and automation
- `references/troubleshooting.md` - Detailed troubleshooting guide for common issues and solutions

The download contains SKILL.md . Extract the whole bundle; the supporting files are required. Inspect the included MANIFEST.json for file hashes.

By **HashiCorp**. [Exact upstream source ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks/SKILL.md) · [Licence](/resources/skills/hashicorp-terraform-stacks/LICENSE.txt) · [Attribution](/resources/skills/hashicorp-terraform-stacks/ATTRIBUTION.txt)

SHA-256 2ccf67ec434439133b83b7905c8846e4f7b1fd99c360b35f884f189ffcb8e091

 Read the applicable licence Mozilla Public License Version 2.0
==================================

1. Definitions
--------------

1.1. "Contributor"
 means each individual or legal entity that creates, contributes to
 the creation of, or owns Covered Software.

1.2. "Contributor Version"
 means the combination of the Contributions of others (if any) used
 by a Contributor and that particular Contributor's Contribution.

1.3. "Contribution"
 means Covered Software of a particular Contributor.

1.4. "Covered Software"
 means Source Code Form to which the initial Contributor has attached
 the notice in Exhibit A, the Executable Form of such Source Code
 Form, and Modifications of such Source Code Form, in each case
 including portions thereof.

1.5. "Incompatible With Secondary Licenses"
 means

 (a) that the initial Contributor has attached the notice described
 in Exhibit B to the Covered Software; or

 (b) that the Covered Software was made available under the terms of
 version 1.1 or earlier of the License, but not also under the
 terms of a Secondary License.

1.6. "Executable Form"
 means any form of the work other than Source Code Form.

1.7. "Larger Work"
 means a work that combines Covered Software with other material, in
 a separate file or files, that is not Covered Software.

1.8. "License"
 means this document.

1.9. "Licensable"
 means having the right to grant, to the maximum extent possible,
 whether at the time of the initial grant or subsequently, any and
 all of the rights conveyed by this License.

1.10. "Modifications"
 means any of the following:

 (a) any file in Source Code Form that results from an addition to,
 deletion from, or modification of the contents of Covered
 Software; or

 (b) any new file in Source Code Form that contains any Covered
 Software.

1.11. "Patent Claims" of a Contributor
 means any patent claim(s), including without limitation, method,
 process, and apparatus claims, in any patent Licensable by such
 Contributor that would be infringed, but for the grant of the
 License, by the making, using, selling, offering for sale, having
 made, import, or transfer of either its Contributions or its
 Contributor Version.

1.12. "Secondary License"
 means either the GNU General Public License, Version 2.0, the GNU
 Lesser General Public License, Version 2.1, the GNU Affero General
 Public License, Version 3.0, or any later versions of those
 licenses.

1.13. "Source Code Form"
 means the form of the work preferred for making modifications.

1.14. "You" (or "Your")
 means an individual or a legal entity exercising rights under this
 License. For legal entities, "You" includes any entity that
 controls, is controlled by, or is under common control with You. For
 purposes of this definition, "control" means (a) the power, direct
 or indirect, to cause the direction or management of such entity,
 whether by contract or otherwise, or (b) ownership of more than
 fifty percent (50%) of the outstanding shares or beneficial
 ownership of such entity.

2. License Grants and Conditions
--------------------------------

2.1. Grants

Each Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license:

(a) under intellectual property rights (other than patent or trademark)
 Licensable by such Contributor to use, reproduce, make available,
 modify, display, perform, distribute, and otherwise exploit its
 Contributions, either on an unmodified basis, with Modifications, or
 as part of a Larger Work; and

(b) under Patent Claims of such Contributor to make, use, sell, offer
 for sale, have made, import, and otherwise transfer either its
 Contributions or its Contributor Version.

2.2. Effective Date

The licenses granted in Section 2.1 with respect to any Contribution
become effective for each Contribution on the date the Contributor first
distributes such Contribution.

2.3. Limitations on Grant Scope

The licenses granted in this Section 2 are the only rights granted under
this License. No additional rights or licenses will be implied from the
distribution or licensing of Covered Software under this License.
Notwithstanding Section 2.1(b) above, no patent license is granted by a
Contributor:

(a) for any code that a Contributor has removed from Covered Software;
 or

(b) for infringements caused by: (i) Your and any other third party's
 modifications of Covered Software, or (ii) the combination of its
 Contributions with other software (except as part of its Contributor
 Version); or

(c) under Patent Claims infringed by Covered Software in the absence of
 its Contributions.

This License does not grant any rights in the trademarks, service marks,
or logos of any Contributor (except as may be necessary to comply with
the notice requirements in Section 3.4).

2.4. Subsequent Licenses

No Contributor makes additional grants as a result of Your choice to
distribute the Covered Software under a subsequent version of this
License (see Section 10.2) or under the terms of a Secondary License (if
permitted under the terms of Section 3.3).

2.5. Representation

Each Contributor represents that the Contributor believes its
Contributions are its original creation(s) or it has sufficient rights
to grant the rights to its Contributions conveyed by this License.

2.6. Fair Use

This License is not intended to limit any rights You have under
applicable copyright doctrines of fair use, fair dealing, or other
equivalents.

2.7. Conditions

Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
in Section 2.1.

3. Responsibilities
-------------------

3.1. Distribution of Source Form

All distribution of Covered Software in Source Code Form, including any
Modifications that You create or to which You contribute, must be under
the terms of this License. You must inform recipients that the Source
Code Form of the Covered Software is governed by the terms of this
License, and how they can obtain a copy of this License. You may not
attempt to alter or restrict the recipients' rights in the Source Code
Form.

3.2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

(a) such Covered Software must also be made available in Source Code
 Form, as described in Section 3.1, and You must inform recipients of
 the Executable Form how they can obtain a copy of such Source Code
 Form by reasonable means in a timely manner, at a charge no more
 than the cost of distribution to the recipient; and

(b) You may distribute such Executable Form under the terms of this
 License, or sublicense it under different terms, provided that the
 license for the Executable Form does not attempt to limit or alter
 the recipients' rights in the Source Code Form under this License.

3.3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice,
provided that You also comply with the requirements of this License for
the Covered Software. If the Larger Work is a combination of Covered
Software with a work governed by one or more Secondary Licenses, and the
Covered Software is not Incompatible With Secondary Licenses, this
License permits You to additionally distribute such Covered Software
under the terms of such Secondary License(s), so that the recipient of
the Larger Work may, at their option, further distribute the Covered
Software under the terms of either this License or such Secondary
License(s).

3.4. Notices

You may not remove or alter the substance of any license notices
(including copyright notices, patent notices, disclaimers of warranty,
or limitations of liability) contained within the Source Code Form of
the Covered Software, except that You may alter any license notices to
the extent required to remedy known factual inaccuracies.

3.5. Application of Additional Terms

You may choose to offer, and to charge a fee for, warranty, support,
indemnity or liability obligations to one or more recipients of Covered
Software. However, You may do so only on Your own behalf, and not on
behalf of any Contributor. You must make it absolutely clear that any
such warranty, support, indemnity, or liability obligation is offered by
You alone, and You hereby agree to indemnify every Contributor for any
liability incurred by such Contributor as a result of warranty, support,
indemnity or liability terms You offer. You may include additional
disclaimers of warranty and limitations of liability specific to any
jurisdiction.

4. Inability to Comply Due to Statute or Regulation
---------------------------------------------------

If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Software due to
statute, judicial order, or regulation then You must: (a) comply with
the terms of this License to the maximum extent possible; and (b)
describe the limitations and the code they affect. Such description must
be placed in a text file included with all distributions of the Covered
Software under this License. Except to the extent prohibited by statute
or regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.

5. Termination
--------------

5.1. The rights granted under this License will terminate automatically
if You fail to comply with any of its terms. However, if You become
compliant, then the rights granted under this License from a particular
Contributor are reinstated (a) provisionally, unless and until such
Contributor explicitly and finally terminates Your grants, and (b) on an
ongoing basis, if such Contributor fails to notify You of the
non-compliance by some reasonable means prior to 60 days after You have
come back into compliance. Moreover, Your grants from a particular
Contributor are reinstated on an ongoing basis if such Contributor
notifies You of the non-compliance by some reasonable means, this is the
first time You have received notice of non-compliance with this License
from such Contributor, and You become compliant prior to 30 days after
Your receipt of the notice.

5.2. If You initiate litigation against any entity by asserting a patent
infringement claim (excluding declaratory judgment actions,
counter-claims, and cross-claims) alleging that a Contributor Version
directly or indirectly infringes any patent, then the rights granted to
You by any and all Contributors for the Covered Software under Section
2.1 of this License shall terminate.

5.3. In the event of termination under Sections 5.1 or 5.2 above, all
end user license agreements (excluding distributors and resellers) which
have been validly granted by You or Your distributors under this License
prior to termination shall survive termination.

************************************************************************
* *
* 6. Disclaimer of Warranty *
* ------------------------- *
* *
* Covered Software is provided under this License on an "as is" *
* basis, without warranty of any kind, either expressed, implied, or *
* statutory, including, without limitation, warranties that the *
* Covered Software is free of defects, merchantable, fit for a *
* particular purpose or non-infringing. The entire risk as to the *
* quality and performance of the Covered Software is with You. *
* Should any Covered Software prove defective in any respect, You *
* (not any Contributor) assume the cost of any necessary servicing, *
* repair, or correction. This disclaimer of warranty constitutes an *
* essential part of this License. No use of any Covered Software is *
* authorized under this License except under this disclaimer. *
* *
************************************************************************

************************************************************************
* *
* 7. Limitation of Liability *
* -------------------------- *
* *
* Under no circumstances and under no legal theory, whether tort *
* (including negligence), contract, or otherwise, shall any *
* Contributor, or anyone who distributes Covered Software as *
* permitted above, be liable to You for any direct, indirect, *
* special, incidental, or consequential damages of any character *
* including, without limitation, damages for lost profits, loss of *
* goodwill, work stoppage, computer failure or malfunction, or any *
* and all other commercial damages or losses, even if such party *
* shall have been informed of the possibility of such damages. This *
* limitation of liability shall not apply to liability for death or *
* personal injury resulting from such party's negligence to the *
* extent applicable law prohibits such limitation. Some *
* jurisdictions do not allow the exclusion or limitation of *
* incidental or consequential damages, so this exclusion and *
* limitation may not apply to You. *
* *
************************************************************************

8. Litigation
-------------

Any litigation relating to this License may be brought only in the
courts of a jurisdiction where the defendant maintains its principal
place of business and such litigation shall be governed by laws of that
jurisdiction, without reference to its conflict-of-law provisions.
Nothing in this Section shall prevent a party's ability to bring
cross-claims or counter-claims.

9. Miscellaneous
----------------

This License represents the complete agreement concerning the subject
matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent
necessary to make it enforceable. Any law or regulation which provides
that the language of a contract shall be construed against the drafter
shall not be used to construe this License against a Contributor.

10. Versions of the License
---------------------------

10.1. New Versions

Mozilla Foundation is the license steward. Except as provided in Section
10.3, no one other than the license steward has the right to modify or
publish new versions of this License. Each version will be given a
distinguishing version number.

10.2. Effect of New Versions

You may distribute the Covered Software under the terms of the version
of the License under which You originally received the Covered Software,
or under the terms of any subsequent version published by the license
steward.

10.3. Modified Versions

If you create software not governed by this License, and you want to
create a new license for such software, you may create and use a
modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that
such modified license differs from this License).

10.4. Distributing Source Code Form that is Incompatible With Secondary
Licenses

If You choose to distribute Source Code Form that is Incompatible With
Secondary Licenses under the terms of this version of the License, the
notice described in Exhibit B of this License must be attached.

Exhibit A - Source Code Form License Notice
-------------------------------------------

 This Source Code Form is subject to the terms of the Mozilla Public
 License, v. 2.0. If a copy of the MPL was not distributed with this
 file, You can obtain one at https://mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely to look
for such a notice.

You may add additional accurate notices of copyright ownership.

Exhibit B - "Incompatible With Secondary Licenses" Notice
---------------------------------------------------------

 This Source Code Form is "Incompatible With Secondary Licenses", as
 defined by the Mozilla Public License, v. 2.0.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks/SKILL.md) Checked 2026-10-14 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks/SKILL.md Supports: Workflow and stated scope
- [Repository licence ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE) Checked 2026-10-07 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE Supports: Redistribution terms
- [Install instructions ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md) Checked 2026-10-07 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md Supports: Documented install path
- [Pinned continuation review C2-W48 ↗](https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/terraform-stacks/SKILL.md Supports: review.findings, bestFor, limitations

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Provider actions ↗ Guides Terraform Plugin Framework action registration, configuration and lifecycle-trigger integration.](/skills/hashicorp-provider-actions/)[### Provider configuration ↗ Builds a provider Configure method as a credential chain and names every source a failed login tried.](/skills/hashicorp-provider-configuration/)[### Provider framework migration ↗ Starts by asking whether to migrate at all, then muxes the provider and verifies before claiming the port is done.](/skills/hashicorp-provider-framework-migration/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)