Terragrunt for DRY configurations in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does DRY stand for in Terragrunt configurations?

DRY stands for "Don't Repeat Yourself." It means writing code or configurations once and reusing them to avoid duplication.

beginner

How does Terragrunt help with DRY in Terraform projects?

Terragrunt lets you keep common Terraform code in one place and reuse it across many modules, so you don't copy-paste the same code multiple times.

beginner

What is a common file used by Terragrunt to define reusable configurations?

Terragrunt uses a file called terragrunt.hcl to store reusable settings like backend configs and variables.

intermediate

What is the purpose of the include block in a Terragrunt configuration?

The include block lets a Terragrunt config reuse settings from a parent or common config file, helping keep things DRY.

intermediate

Why is using Terragrunt beneficial for managing multiple Terraform environments?

Terragrunt helps manage multiple environments by sharing common configs and only changing what’s different, making updates easier and less error-prone.

What is the main goal of using Terragrunt with Terraform?

A To avoid repeating configuration code

B To replace Terraform completely

C To write Terraform code in a new language

D To deploy applications faster

Terragrunt is designed to help avoid repeating Terraform configuration code by enabling reuse and better organization.

Which file does Terragrunt use to store reusable configuration blocks?

A terraform.tfstate

B main.tf

C terragrunt.hcl

D variables.tf

Terragrunt uses the terragrunt.hcl file to define reusable configuration blocks.

What does the include block in Terragrunt do?

A Creates new Terraform modules

B Runs Terraform commands automatically

C Defines variables for Terraform

D Imports settings from another Terragrunt config

The include block imports settings from another Terragrunt configuration file to reuse common settings.

How does Terragrunt help when managing multiple environments like dev and prod?

A By merging all environments into one

B By sharing common configs and only changing environment-specific parts

C By deleting unused environments automatically

D By converting Terraform code to scripts

Terragrunt helps manage multiple environments by sharing common configurations and customizing only what differs.

Which of these is NOT a benefit of using Terragrunt?

A Replacing Terraform's core engine

B Simplifying Terraform configuration management

C Avoiding code duplication

D Easier environment management

Terragrunt does not replace Terraform's core engine; it works alongside Terraform to improve configuration management.

Explain how Terragrunt helps keep Terraform configurations DRY and why this is useful.

Think about how copying code can cause mistakes and how sharing code helps.

Describe the role of the include block in Terragrunt and how it supports configuration reuse.

It's like inheriting settings from a shared file.