terraform-azurerm-set-diff-analyzer

To filter false-positive Terraform plan diffs for AzureRM Set-type attributes, parse the plan JSON to detect order-only changes versus actual additions or removals in resources like Application Gateways or Load Balancers. This separates real resource changes from irrelevant ordering shifts.

False-positive diffs in AzureRM Terraform plans are caused by Set-type attributes, where the provider detects reordering of elements as changes. The analyzer identifies these order-only differences across nested attributes in resources like NSGs and Front Doors to isolate actual additions or removals.

To analyze a Terraform plan JSON for Set-diff false positives, first generate a plan file and convert it to JSON using terraform show -json. Then run the Python analysis script against the JSON output, using a JSON attribute map to drive comparisons and output structured results.

Yes, the AzureRM Set-diff analyzer handles nested Set attributes and keys across complex resources such as application gateways, firewall policies, and front doors. It processes these nested structures within the Terraform plan JSON to accurately separate ordering changes from real diffs.

Yes, you can integrate Terraform Set-diff analysis into CI/CD pipelines. The analyzer processes the plan JSON and outputs structured results suitable for downstream tooling and dashboards, producing concise summaries and actionable reports to help teams focus on real resource changes.

To run the AzureRM Terraform false-positive diff analyzer, you need Python 3.8 or higher and a JSON attribute map located at references/azurerm_set_attributes.json. You also need a Terraform plan exported as JSON to serve as the input for the analysis script.