Terraform Stack CLI reference

The terraform-stacks-cli is a command-line tool for validating, initializing, and testing Stack configurations.

Requirements

The terraform-stacks-cli requires an alpha version of Terraform, and you must use at least terraform_1.10.0-alpha20241009 or higher. You can download an alpha version of Terraform on the releases page.

Installation

To install the terraform-stacks-cli, you can download it directly on the HashiCorp releases page or install it with one of the following package managers: Homebrew, Debian/Ubuntu, CentOS/RHEL, Fedora, or Amazon Linux.

Homebrew

Run the following commands to install the terraform-stacks-cli using Homebrew.

$ brew tap hashicorp/tap
$ brew install hashicorp/tap/tfstacks

Linux Package Managers

Run the following commands to install the terraform-stacks-cli with the following Linux package managers.

Debian or Ubuntu

Run the following commands to install the terraform-stacks-cli using Debian or Ubuntu.

$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
$ sudo apt update && sudo apt install terraform-stacks-cli

CentOS or RHEL

Run the following commands to install the terraform-stacks-cli using CentOS or RHEL.

$ sudo yum install -y yum-utils
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
$ sudo yum -y install terraform-stacks-cli

Fedora

Run the following commands to install the terraform-stacks-cli using Fedora.

$ sudo dnf install -y dnf-plugins-core
$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
$ sudo dnf -y install terraform-stacks-cli

Amazon Linux

Run the following commands to install the terraform-stacks-cli using Amazon Linux.

$ sudo yum install -y yum-utils shadow-utils
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
$ sudo yum -y install terraform-stacks-cli

Commands

The terraform-stacks-cli supports the following four commands:

Each Stack command supports global options.

`tfstacks init` command

The tfstacks init command attempts to download any dependencies your Stack configuration requires.

$ tfstacks init

If the tfstacks init command cannot find a dependency, it warns you of the reason why and installs a false dependency in the real one's place to unblock any future validation. Meaning, that it the tfstacks init command cannot download a dependency, you can still run tfstacks validate, but the missing dependencies are not validated.

`tfstacks validate` command

The tfstacks validate command loads your Stack configuration and validates that your stack’s syntax and static types are correct.

$ tfstacks validate

We recommend running this command whenever you change your Stack configuration.

`tfstacks providers lock` command

The tfstacks providers lock command creates and updates your stack’s provider lock file.

$ tfstacks providers lock [-platform=os_arch]

The tfstacks providers lock command references the required_providers block from your configuration to know which providers to download and compute the provider lock hashes for. The tfstacks providers lock command only checks the required_providers block, so you must list all of the providers you use in the required_providers block to ensure that the tfstacks providers lock command can find them.

By default, the tfstacks providers lock installs hashes for providers built for linux_amd64 machines, which HCP Terraform requires for execution. You can optionally use the -platform=os_arch argument to create hashes for other platforms.

`tfstacks plan` command

The tfstacks plan runs a remote, speculative plan with local code in the current directory. If you are not currently logged in to HCP Terraform when you run this command, the output prompts you to log in.

$ tfstacks plan -organization=REQUIRED_ORG_NAME -stack=REQUIRED_STACK_ID -deployment=REQUIRED_DEPLOYMENT [-hostname=hostname]

The tfstacks plan accepts the following arguments.

Field	Description	Required
`-organization`	Set the `organization` flag to the name of this stack’s organization. Alternatively, you can set an environment variable named `TFSTACKS_ORGANIZATION` with the same value.	Required
`-stack=`	Set the `stack` flag to the ID of the Stack you want to perform this plan in. You can find a stack’s ID underneath its name when you view that Stack in HCP Terraform. Alternatively, you can set an environment variable named `TFSTACKS_STACK_ID` with the same value.	Required
`-deployment=`	Set the `deployment` flag to the deployment name you want to perform this plan in. The deployment name must match one of the deployment names you specified in the `tfdeploy.hcl` file. Alternatively, you can set an environment variable named `TFSTACKS_DEPLOYMENT` with the same value.	Required
`-hostname=`	You can set the `hostname` flag to the hostname of the HCP Terraform instance you want to perform this plan in. The default value is `app.terraform.io`. Alternatively, you can set an environment variable named `TFSTACKS_HOSTNAME` with the same value.	Optional

Global options

You can apply the following global options to any tfstacks command:

The -terraform-binary flag specifies a specific version of Terraform to use instead of the one in your PATH.
The -chdir flag points to an alternate configuration directory.
The -no-color flag disables color output in the CLI.