terraform-style-check

To enforce Terraform style guidelines, you apply rules for two-space indentation, descriptive variable names with types and descriptions, and version pinning. This ensures consistency and safety across infrastructure configurations.

The recommended Terraform file structure organizes configurations into standard files like variables.tf, main.tf, and outputs.tf. This organization improves maintainability and reduces code drift across modules.

To ensure security best practices in Terraform, enforce secure defaults, version pinning, and outputs with descriptions. This applies to creating, reviewing, and maintaining infrastructure code.

Yes, you can validate existing Terraform configurations by checking for common tooling guidance and reviewing against style conventions. This covers file organization, variable naming, and resource layout.

The best way to generate a compliant Terraform module is to follow the style guide for a simple VPC example. This enforces naming conventions, indentation, and standard file structures.

Terraform configurations need descriptive variable names and types to improve consistency and safety. This practice ensures maintainability and aligns with official style conventions.