terraform-azurerm-set-diff-analyzer

Analyze Terraform plan JSON to distinguish order-only Set-type diffs from actual AzureRM resource changes.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill terraform-azurerm-set-diff-analyzer-gabeujin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-azurerm-set-diff-analyzer
Source: https://github.com/Gabeujin/workspace-init-mcp/tree/main/awesome/skills/terraform-azurerm-set-diff-analyzer
Command: npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill terraform-azurerm-set-diff-analyzer-gabeujin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you distinguish between actual changes and "false-positive diffs" in Terraform plans for AzureRM resources, specifically those caused by the ordering of elements within Set-type attributes.

Core Features & Use Cases

  • Identify Order-Only Diffs: Automatically detects changes in Set-type attributes (like security_rule in NSGs or backend_address_pool in App Gateways) that are merely due to element reordering and have no real impact.
  • Filter Spurious Changes: Reduces noise in terraform plan output, making reviews faster and more accurate.
  • Use Case: When reviewing a Terraform plan for an Azure Application Gateway, you see that all backend_address_pool elements are marked as changed. This Skill can confirm if this is just an order change or if an actual backend address was added/removed.

Quick Start

Use the terraform-azurerm-set-diff-analyzer skill to analyze the terraform plan JSON file named 'plan.json'.

Frequently Asked Questions about terraform-azurerm-set-diff-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Terraform plan show changes for Azure Application Gateway backend_address_pool when I didn't modify any addresses?

Terraform plan shows changes for Azure Application Gateway backend_address_pool because the AzureRM provider often detects order-only diffs in Set-type attributes. This analyzer filters those spurious changes by verifying if elements were merely reordered.

How do I filter out false-positive diffs in Terraform plan JSON for Azure resources?

You filter false-positive diffs in Terraform plan JSON by running this analyzer against the file. It parses the plan output to detect and exclude order-only changes in Set-type attributes, reducing noise for faster reviews.

What is an order-only diff in Set-type attributes for AzureRM Terraform resources?

An order-only diff in Set-type attributes occurs when Terraform detects element reordering as a change, despite no actual modifications. This happens frequently with AzureRM resources like Network Security Groups and Load Balancers.

Does the AzureRM Terraform set diff analyzer support Network Security Group security_rule changes?

Yes, the AzureRM Terraform set diff analyzer supports Network Security Group security_rule changes. It specifically evaluates Set-type attributes for NSGs, Application Gateways, and Load Balancers to confirm whether changes are actual modifications.

Do I need Python to analyze Terraform plan JSON for AzureRM set attribute diffs?

Yes, you need Python 3.8 or higher installed to execute the analyzer script. It processes the Terraform plan JSON file locally to differentiate between actual resource modifications and order-only attribute changes.