Step 4b: Pre-Flight AVM-TF Check - terraform-e2e

✅ Step 4b: Pre-Flight AVM-TF Check - terraform-e2e

• 🎯 Purpose
• ✅ AVM Schema Validation Results
• � Provider Version Resolution
• 🔎 Parameter Type Analysis
• 📋 Variable Schema Cross-Validation
• 🌍 Region Limitations Identified
• ⚠️ Pitfalls Checklist
• 🚀 Ready for Implementation

Generated by terraform-code agent | 2026-02-26 Source: Terraform Registry MCP (search_modules → get_module_details → get_latest_module_version) Status: PASS

🎯 Purpose

[!IMPORTANT] This checkpoint validates AVM-TF module schemas BEFORE Terraform code generation by querying the Terraform Registry for latest versions and variable schemas.

Prevents:

• Variable type mismatches (e.g., parent_id vs resource_group_name)
• Deprecated variable usage
• Region availability issues
• Missing required variables
• Version constraint drift

✅ AVM Schema Validation Results

%%{init: {'theme':'neutral'}}%%
flowchart LR
    A["Discover AVM-TF\nModules"] --> B["Validate\nSchema"]
    B --> C["Check\nVariables"]
    C --> D["Verify\nRegions"]
    D --> E{"Pass?"}
    E -- Yes --> F["✅ Ready"]
    E -- No --> G["❌ Blocked"]
    style F fill:#107C10,color:#fff
    style G fill:#D83B01,color:#fff

Version Match: All ~> pessimistic version constraints resolve to latest available versions within their bands.

Download Counts (Module Adoption)

🔗 Provider Version Resolution

🔎 Parameter Type Analysis

Required Variables per Module (Registry-Sourced)

Optional variables used:

⚠️ Pitfall Avoided: Variable is workspace_id — NOT workspace_resource_id.

Optional variables used:

⚠️ Pitfall Avoided: No enable_rbac_authorization variable exists. RBAC is the default when legacy_access_policies_enabled = false (module default).

Optional variables used:

⚠️ Pitfall Avoided: Variable is soft_delete_retention_days — NOT soft_delete_retention_in_days.

⚠️ Pitfall Avoided: minimum_tls_version is hardcoded to "1.2" in the AVM module — NOT a variable.

Optional variables used:

⚠️ Pitfall Avoided: Uses parent_id (resource group ID) — NOT resource_group_name.

Optional variables used:

⚠️ Pitfall Avoided: Uses parent_id (resource group ID) — NOT resource_group_name.

Optional variables used:

📋 Variable Schema Cross-Validation

Cross-validation of every variable used in main.tf against registry-sourced module schemas:

Local Validation

🌍 Region Limitations Identified

All resources are available in swedencentral. No region overrides required.

⚠️ Pitfalls Checklist

Based on AVM Known Pitfalls (terraform-patterns skill) and registry schema validation:

• App Service Plan uses parent_id (resource group ID) — not resource_group_name
• App Service uses parent_id (resource group ID) — not resource_group_name
• App Insights uses workspace_id — not workspace_resource_id
• Key Vault does NOT have enable_rbac_authorization — RBAC enabled via legacy_access_policies_enabled = false (default)
• Key Vault uses soft_delete_retention_days — not soft_delete_retention_in_days
• SQL Server requires server_version = "12.0" — minimum_tls_version is hardcoded in module
• App Service uses application_insights_connection_string (not deprecated instrumentation key)
• No Storage Account names contain hyphens
• All ~> version pins resolve to published versions within their constraint bands
• azurerm provider pinned ~> 4.0 — latest 4.61.0 compatible

🚀 Ready for Implementation

[!IMPORTANT] Go / No-Go Verdict

Signal	Status
AVM Modules	✅
Provider Versions	✅
Variable Schemas	✅
Regions	✅
Pitfalls	✅
terraform validate	✅
Overall	✅ READY

Pre-flight validation for terraform-e2e Terraform implementation. Registry data sourced via Terraform MCP: get_latest_module_version, get_module_details, get_latest_provider_version.