terragrunt-validator

You can validate Terragrunt configurations by running automated checks for HCL formatting, syntax, Terraform validation, linting via tflint, and security scanning with Trivy in a deterministic CI workflow.

End-to-end Terragrunt validation includes HCL format checking, input validation, Terragrunt syntax verification, Terraform validation, tflint linting, security scanning, and dependency graph checks across your project layouts.

Yes, you can run Terragrunt linting and security scans on multi-unit directories, single units, and root-only layouts, executing checks across all applicable configuration files simultaneously.

The best way to automate formatting checks is using a deterministic workflow that runs terragrunt hcl fmt and terragrunt hcl validate to enforce consistent HCL structure across your infrastructure code.

Yes, the Terragrunt validation workflow supports security scanning with Trivy or alternative security scanners to identify vulnerabilities and enforce infrastructure security best practices.

Dependency graph checks in Terragrunt projects ensure that module dependencies are correctly defined and ordered, preventing deployment failures caused by missing or misconfigured infrastructure dependencies.