terraform-azurerm-set-diff-analyzer

To filter false-positive Terraform plan diffs caused by AzureRM Set attribute ordering, analyze your plan JSON output to distinguish between order-only changes in Set-type attributes and actual resource modifications. This highlights only real additions, removals, or replacements.

Your Terraform plan shows dozens of changes because AzureRM Set-type attributes like backend_address pools generate false-positive diffs when element ordering shifts. Analyzing the plan JSON filters these noise changes, showing that only one element was truly affected.

Yes, you can integrate Terraform AzureRM plan analysis into your CI/CD pipeline by processing the plan JSON output with optional exit codes. This allows your automation workflow to fail or pass based on actual resource modifications rather than false-positive Set diffs.

Available output formats when analyzing Terraform plan JSON for AzureRM Set diffs include markdown, JSON, and summary formats. These options allow you to easily integrate the filtered plan analysis results into your existing review workflows or automation reports.

Yes, this Terraform plan analysis works for Azure Network Security Group security_rule changes by specifically targeting Set-type attributes. It effectively filters out false-positive diffs caused by rule reordering, ensuring your plan review focuses only on actual security rule additions or modifications.