Terragrunt Stack — One Blueprint for Every Environment (Terraform Course #9)
academeez
111 views
Build reusable prod and non-prod environments from a single terragrunt.stack.hcl blueprint, instead of copying a folder tree for every environment.
Prod is built for high availability. Non-prod is built for cost. This lesson creates the folder and the project. Later lessons add the VPC, database, and GKE cluster.
📖 Full lesson article:
https://www.academeez.com/courses/ter...
This is lesson 9 in the Terraform / OpenTofu / Terragrunt course.
Related lessons
🎬 Terragrunt Catalog video (10:10): Terragrunt Catalog — Build a Reusable IaC ...
📄 Terragrunt Catalog lesson (21:02): https://www.academeez.com/courses/ter...
🎬 Terragrunt Units video (12:01): Advanced Terraform and IAC lesson 7: Terra...
Docs
🧱 What is a Terralith? (14:25): https://docs.terragrunt.com/guides/te...
Implicit stacks (21:25): https://docs.terragrunt.com/features/...
Explicit stacks (25:04): https://docs.terragrunt.com/features/...
Migrating implicit stacks to explicit stacks (37:43): https://docs.terragrunt.com/migrate/t...
#Terragrunt #Terraform #OpenTofu #IaC #DevOps
Chapters
0:00:00 Introduction — creating environments with Terragrunt stacks
0:01:06 Lesson goals — prod vs non-prod (availability vs cost)
0:05:40 The full lesson article on academeez
0:06:49 Environment architecture: folder, project, VPC, GKE and database
0:11:55 Why not build the environment as one unit: avoiding a Terralith
0:17:08 Implicit stacks: duplicated folders and units per environment
0:24:43 Explicit stacks: one terragrunt.stack.hcl blueprint
0:27:23 Coding: first terragrunt.stack.hcl with two GCP folders
0:35:36 terragrunt stack generate: output files and in-place migration
0:40:15 Catalog stacks: moving the two-folder stack into the catalog
0:50:05 Coding: values for placeholders in a catalog stack
0:53:48 autoinclude: place a project unit inside a folder unit
1:12:16 Coding: default folder and project inputs, with overrides
1:19:37 The stack block: one file calling the catalog env stack
1:25:27 autoinclude on the stack block
1:31:19 Place the env under the root folder, then generate live envs
1:39:09 Summary
Terragrunt Stack — One Blueprint for Every Environment (Terraform Course #9)
academeez
111 views
Build reusable prod and non-prod environments from a single terragrunt.stack.hcl blueprint, instead of copying a folder tree for every environment.
Prod is built for high availability. Non-prod is built for cost. This lesson creates the folder and the project. Later lessons add the VPC, database, and GKE cluster.
📖 Full lesson article:
https://www.academeez.com/courses/ter...
This is lesson 9 in the Terraform / OpenTofu / Terragrunt course.
Related lessons
🎬 Terragrunt Catalog video (10:10): Terragrunt Catalog — Build a Reusable IaC ...
📄 Terragrunt Catalog lesson (21:02): https://www.academeez.com/courses/ter...
🎬 Terragrunt Units video (12:01): Advanced Terraform and IAC lesson 7: Terra...
Docs
🧱 What is a Terralith? (14:25): https://docs.terragrunt.com/guides/te...
Implicit stacks (21:25): https://docs.terragrunt.com/features/...
Explicit stacks (25:04): https://docs.terragrunt.com/features/...
Migrating implicit stacks to explicit stacks (37:43): https://docs.terragrunt.com/migrate/t...
#Terragrunt #Terraform #OpenTofu #IaC #DevOps
Chapters
0:00:00 Introduction — creating environments with Terragrunt stacks
0:01:06 Lesson goals — prod vs non-prod (availability vs cost)
0:05:40 The full lesson article on academeez
0:06:49 Environment architecture: folder, project, VPC, GKE and database
0:11:55 Why not build the environment as one unit: avoiding a Terralith
0:17:08 Implicit stacks: duplicated folders and units per environment
0:24:43 Explicit stacks: one terragrunt.stack.hcl blueprint
0:27:23 Coding: first terragrunt.stack.hcl with two GCP folders
0:35:36 terragrunt stack generate: output files and in-place migration
0:40:15 Catalog stacks: moving the two-folder stack into the catalog
0:50:05 Coding: values for placeholders in a catalog stack
0:53:48 autoinclude: place a project unit inside a folder unit
1:12:16 Coding: default folder and project inputs, with overrides
1:19:37 The stack block: one file calling the catalog env stack
1:25:27 autoinclude on the stack block
1:31:19 Place the env under the root folder, then generate live envs
1:39:09 Summary