Terraform忽略VPC对等连接资源创建问题求助

Hey there, let's work through this frustrating issue where your VPC peering connection is being ignored, and you're hitting an error when trying to reference it in outputs. Here are targeted steps to diagnose and fix the problem:

1. Verify Resource Block Syntax & Module Visibility #

First, nail down the basics:

• Double-check that your aws_vpc_peering_connection resource block in the network module has no typos (misspelling the resource type is easier than you think!).
• Remember: Terraform modules don't expose internal resources by default. If you're referencing this resource from outside the module, you need to explicitly define an output in the network module first:

  # Inside network module's outputs.tf
  output "vpc_peering_connection_id" {
    value = aws_vpc_peering_connection.default.id
  }
  

  Then reference it in your root module as module.network.vpc_peering_connection_id instead of directly calling aws_vpc_peering_connection.default.id.

2. Check for Conditional Creation Logic #

If your peering connection uses count or for_each to conditionally create it, confirm the conditions are being met:

• For example, if you have code like this:

  resource "aws_vpc_peering_connection" "default" {
    count = var.enable_vpc_peering ? 1 : 0
    # ... other required arguments
  }
  

  Make sure var.enable_vpc_peering is set to true in your module call. If count evaluates to 0, the resource won't exist, and referencing it will throw the "not declared" error.
• In Terraform 0.12+, for_each has similar behavior—verify the map/list used for for_each isn't empty.

3. Inspect Terraform State & Configuration Validity #

• Run terraform state list to see if the peering connection resource appears in the state. If it's missing entirely, Terraform isn't recognizing the resource block at all.
• Run terraform validate on your configuration to catch any syntax errors that might be causing Terraform to skip the resource block. Small issues like missing commas or incorrect variable references can lead to silent failures.

4. Validate Module Inputs & Internal Logic #

If your network module creates the peering connection only when specific inputs are provided:

• Confirm you're passing all required variables to the module (e.g., peer VPC ID, cross-account owner ID if applicable). Missing required arguments might cause Terraform to ignore the resource.
• Review the module's internal logic—check for a depends_on that's misconfigured, or a variable default that's accidentally disabling peering creation.

5. Rule Out 0.11 to 0.12 Migration Quirks #

Even though you upgraded to 0.12.3, double-check for migration-related issues:

• Terraform 0.12 introduced stricter syntax rules. While 0.11-style ${var.name} references still work, leftover conflicting syntax could cause unexpected behavior.
• Ensure your network module is compatible with 0.12—if it was originally written for 0.11, subtle incompatibilities might be causing resource blocks to be ignored.

内容的提问来源于stack exchange，提问作者jagatjyoti