Resource count can't reference module variable (Question)

[egarbi]

// This will allow route traffic through the VPC peering
resource "aws_route" "internal" {
  count                     = "${length(module.stack.internal_subnets)}"
  route_table_id            = "${element(split(",", module.stack.internal_route_tables), count.index)}"
  destination_cidr_block    = "10.22.0.0/16"
  vpc_peering_connection_id = "pcx-5660d13f"
}

Error loading Terraform: module root: 1 error(s) occurred:

• aws_route.internal: resource count can't reference module variable: module.stack.internal_subnets

Any idea what I'm doing wrong here?

[achille-roussel]

Which version of terraform you are using?

[egarbi]

@achille-roussel terraform --version
Terraform v0.7.7

[egarbi]

The latest one. 0.7.7

On 20 Oct 2016 6:37 p.m., "Achille" notifications@github.com wrote:

Which version of terraform you are using?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#57 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC2JCUvHCmHZ1YRwossGprkJlkL-CQvdks5q16blgaJpZM4Kb-Oi
.

[achille-roussel]

I guess I'll need to have a better look at the rest of the code, it's not clear from this snippet what could be wrong.

[egarbi]

I think it might be related to this issue in terraform, not 100% sure though

[achille-roussel]

Yeah we've seen issues with the count property when it's computed dynamically in the past, sometimes you can get around it, sometimes not.

[egarbi]

@achille-roussel They fix this in 0.9 so this issue is not there anymore.
Actually, if I run my example above this is the plan proposed:

+ aws_route.internal.0
    destination_cidr_block:     "10.22.0.0/16"
    destination_prefix_list_id: "<computed>"
    egress_only_gateway_id:     "<computed>"
    gateway_id:                 "<computed>"
    instance_id:                "<computed>"
    instance_owner_id:          "<computed>"
    nat_gateway_id:             "<computed>"
    network_interface_id:       "<computed>"
    origin:                     "<computed>"
    route_table_id:             "rtb-40281024"
    state:                      "<computed>"
    vpc_peering_connection_id:  "pcx-5660d13f"

+ aws_route.internal.1
    destination_cidr_block:     "10.22.0.0/16"
    destination_prefix_list_id: "<computed>"
    egress_only_gateway_id:     "<computed>"
    gateway_id:                 "<computed>"
    instance_id:                "<computed>"
    instance_owner_id:          "<computed>"
    nat_gateway_id:             "<computed>"
    network_interface_id:       "<computed>"
    origin:                     "<computed>"
    route_table_id:             "rtb-47281023"
    state:                      "<computed>"
    vpc_peering_connection_id:  "pcx-5660d13f"

+ aws_route.internal.2
    destination_cidr_block:     "10.22.0.0/16"
    destination_prefix_list_id: "<computed>"
    egress_only_gateway_id:     "<computed>"
    gateway_id:                 "<computed>"
    instance_id:                "<computed>"
    instance_owner_id:          "<computed>"
    nat_gateway_id:             "<computed>"
    network_interface_id:       "<computed>"
    origin:                     "<computed>"
    route_table_id:             "rtb-41281025"
    state:                      "<computed>"
    vpc_peering_connection_id:  "pcx-5660d13f"