terraform▌

$23

Comprehensive guide for writing and running Terraform tests with assertions, mocking, and module validation. \n \n Write test files using .tftest.hcl syntax with run blocks that execute in plan or apply mode, supporting sequential and parallel execution with optional state isolation \n Assert conditions on resource attributes, outputs, and data sources; use expect_failures to validate that invalid inputs are properly rejected \n Mock providers (Terraform 1.7.0+) simulate infrastructure behavior

Reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure with standardized patterns and best practices. \n \n Provides pre-built module templates across four cloud providers covering core services like VPC/VNet, Kubernetes clusters, databases, and object storage \n Enforces consistent module structure with input variables, outputs, documentation, examples, and Terratest-based testing \n Includes validation blocks, conditional resources via count/for_each, and tagging strategies for

Generate and maintain Terraform code following HashiCorp's official style conventions. \n \n Enforces two-space indentation, lowercase underscore naming, and standard file organization across terraform.tf , providers.tf , main.tf , variables.tf , outputs.tf , and locals.tf \n Requires type and description on all variables and outputs, with validation rules and sensitive flag support for credentials \n Prioritizes for_each over count for dynamic resources, applies security hardening (encryption,

Identify false-positive diffs in Terraform AzureRM plans caused by Set-type attribute ordering. \n \n Analyzes terraform plan JSON output to distinguish spurious diffs (element reordering in Sets) from actual resource changes \n Targets AzureRM resources with Set-type attributes: Application Gateway, Load Balancer, NSG, Firewall, Front Door, and others \n Requires Python 3.8+ and uses only standard library; integrates into CI/CD pipelines with configurable output formats and exit codes \n Helps