Awesome
<div align="center"> <p><img src=".github/logo.png" width="200px"></p> <h1>Stacks for Terraform</h1> <p>The <a href="https://www.terraform.io/">Terraform</a> code pre-processor</p> </div>What is Stacks for Terraform?
Stacks is a code pre-processor for Terraform. It implements a sustainable scaling pattern, prevents drift and boilerplate, all while plugging into your already existing Terraform pipeline.
Stacks was initially presented at SREcon23 Americas.
Warning: Stacks is under heavy development, many things may change.
What is a "stack"?
- A stack is a set of Terraform resources you want to deploy one or more times.
- Each instance of a stack is a layer. A stack has one or more layers, hence, the name "stacks".
Example
vpc/
│
├── base/
│ ├── vpc.tf
│ └── subnets.tf
│
├── layers/
│ ├── production/
│ │ └── layer.tfvars
│ └── staging/
│ ├── layer.tfvars
│ └── vpn.tf
│
└── stack.tfvars
- This is an example stack called
vpc
. - It contains a
base
folder, containing the common Terraform configuration scoped for all layers in this stack. - It contains a
layers
folder with two layers, one calledproduction
and one calledstaging
. Layer directories contain layer-specific Terraform configuration. - Finally, it contains an optional
stack.tfvars
file, which defines variables global to all layers in the stack. These variables can be overriden at the layer level through a layer-specificlayer.tfvars
.
How does Stacks work?
Stacks sits between you (the Terraform user) and Terraform. It's a code pre-processor. Here's an overview of Stacks inner workings:
- It takes your stack definitions (as shown above)
- For each layer:
- Joins the
base
code with the layer-specific code - Applies a number of transformations
- Injects some extra configuration
- Bundles it up for Terraform to plan/apply on it
How to use Stacks?
First, you need to put the Stacks code somewhere close to your stack definitions. Here's an example (not necessarily what we recommend):
your-terraform-repository/
│
├── src/ # the contents of the `src` directory
│ ├── helpers.py
│ ├── postinit.py
│ └── preinit.py
│
├── environments/ # see the `example` directory on how to set this up
│ ├── production/
│ │ ├── backend.tfvars
│ │ └── environment.tfvars
│ └── staging/
│
└── stacks/ # put your stack definitions here
└── vpc/ # the `vpc` stack shown above
├── base/
│ ├── vpc.tf
│ └── subnets.tf
├── layers/
│ ├── production/
│ │ └── layer.tfvars
│ └── staging/
│ ├── layer.tfvars
│ └── vpn.tf
└── stack.tfvars
You can find another example here with all the appropriate file contents.
Then you need to run Stacks in the layer you want to apply:
cd stacks/vpc/layers/production
python3 ../../../../src/preinit.py
cd stacks.out # where the preinit output goes
terraform init
python3 ../../../../../src/postinit.py
Now you're ready to run any further terraform
commands in the stacks.out
directory.
Note: we recommend putting stacks.out
in .gitignore
to prevent it from being tracked by git.