skip attribute in Terragrunt: a powerful boolean flag that controls whether a specific module runs Terraform commands. By leveraging skip, you can conditionally bypass apply, destroy, and other operations—ideal for tailoring complex infrastructure workflows.
Why Use the skip Attribute?
- Customize multi-module deployments without removing configuration
- Temporarily disable modules under development or testing
- Avoid unintentional changes in non-critical environments
Use the
skip flag to control module execution dynamically, ensuring only ready and tested modules are deployed.Key Considerations
- Skipping critical modules can lead to incomplete infrastructure
- Ensure dependencies are met before disabling a module
Never set
skip = true on production-critical modules. Always verify dependencies to prevent configuration drift.skip Attribute Options
Example: Skipping a VPC Module
Imagine you have a VPC module under development. To prevent Terraform from applying it, addskip = true in your terragrunt.hcl:
terragrunt apply:
skip = true and leaves the VPC unchanged.
Enabling the Module
When you’re ready to deploy, setskip to false or remove it:
skip disabled, Terragrunt proceeds to create the VPC as expected.