Experimental Native Terragrunt Discovery
Teams with working Terragrunt configurations should be able to use Atmos without refactoring those configurations into Atmos conventions. Experimental native Terragrunt support is a step toward that: keep the HCL, units, and stacks you have, and adopt the Atmos capabilities you need alongside them.
The Problem
You already use Terragrunt to manage Terraform. Now you want Atmos for toolchain management, vendoring, scaffolding, authentication, Kubernetes, Helm, and the rest of your infrastructure. You want to use what you have, without first translating every Terragrunt unit into Atmos YAML.
Supporting existing Terragrunt configuration makes Atmos easier to get started with. Teams can adopt it incrementally, without choosing between Atmos and Terragrunt.
Use Atmos with Your Existing Terragrunt Configuration
An explicitly enabled configuration plugin exposes discovered units as Terraform components. Atmos owns execution order, authentication setup, toolchain selection, and working directories. The native path evaluates HCL without launching the Terragrunt executable.
Discovery uses an in-memory expansion for explicit stacks. Planning and applying use isolated Atmos workdirs while preserving the local backend's state path. Projects that do not enable discovery do not scan for Terragrunt configuration.
How to Use It
This implementation requires a local development build; the Terragrunt plugin is not yet published. Follow the package setup and fixture instructions then enable discovery with config set:
atmos config set plugins.packages.terragrunt.path /absolute/path/to/plugins/terragrunt
atmos config set components.terraform.terragrunt.enabled true
atmos config set components.terraform.terragrunt.mode native
atmos config set --type=yaml components.terraform.terragrunt.discovery.included_paths '["live/**"]'
atmos config set components.terraform.terragrunt.discovery.enabled true
Use list instances to inspect the discovered units and Terraform plan to plan them:
atmos list instances
atmos terraform plan --all
Affected selection compares units and dependency relationships at both Git revisions. Shared includes, local module files, and explicit stack definitions can mark their consuming units affected; --include-dependents also follows the dependency graph. Reads inside unevaluated input expressions and arbitrary dynamic glob patterns still need additional source tracking.
The current scope covers local module sources and local backends. Remote sources and backends, Terragrunt hooks, saved-plan apply, and state-function integration remain incomplete. Do not assume full Terragrunt compatibility. The package instructions list the supported and rejected constructs.
Get Involved
Review the Terragrunt integration requirements and help identify configurations that need additional compatibility tests.
