terragrunt-validator

Validate Terragrunt configurations by running a multi-stage process that checks HCL formatting, syntax, input variables, and Terraform configuration. This prevents common misconfigurations and ensures infrastructure-as-code adheres to best practices before merging.

Security scanning on Terraform and Terragrunt is best handled by integrating Trivy or Checkov to identify vulnerabilities. This automated scanning ensures policies are enforced and security issues are caught during validation.

Yes, Terragrunt validation integrates with tflint to enforce coding standards and best practices. This linting stage analyzes your configuration files to catch syntax issues and maintain consistent infrastructure code quality.

Yes, you can preview changes without applying them by performing a dry-run plan. This executes a terragrunt plan to show potential infrastructure modifications safely before any actual deployment occurs.

Yes, Python3, Terragrunt, and Terraform are required dependencies. They provide the execution environment needed to check HCL formatting, validate syntax, analyze module dependency graphs for cycles, and run security scans.

Check multi-module Terragrunt configurations by analyzing the dependency graph during validation. This process detects cycles within module dependencies and ensures complex infrastructure-as-code structures resolve correctly.