terraform-practices

Terraform and OpenTofu testing is structured around native tests for version 1.6+ and Terratest for integration checks. This approach covers static analysis, plan testing, and policy checks to ensure infrastructure code reliability before deployment.

Terraform CI/CD pipelines should include validation, plan, apply, and automated checks with reusable workflows. Environment separation and version management across blueprints ensure consistent module patterns and reliable infrastructure delivery.

Yes, Terraform testing approaches fully support OpenTofu projects. The structured testing and code organization patterns apply to both tools, covering native tests, Terratest guidance, and modern features like try(), moved blocks, optional(), and nullable attributes.

Secure secret handling in Terraform CI/CD requires structured approaches that integrate with environment separation and automated validation checks. This ensures sensitive data is protected during plan and apply operations while maintaining consistent module patterns.

Native Terraform tests suit unit and static analysis checks using version 1.6+ features, while Terratest handles integration testing. Combining both provides comprehensive coverage across plan testing, policy checks, and cross-variable validation for blueprint-style projects.

Standardizing Terraform module patterns requires documentation conventions, versioning, and environment strategies applied across blueprints. This skill evangelizes code patterns including modularization and cross-variable validation to align teams on consistent infrastructure practices.