Execution fails when using `vpc_attachments[].vpc_route_table_ids` about terraform-aws-transit-gateway HOT 29 OPEN

keep alive post

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

Can confirm, we have the same issue.
A two-step apply seems to be the best workaround right now.

from terraform-aws-transit-gateway.

Same here, it does work when replacing the for_each statement with a count, but the trade-off isn't worth it in our opinion.

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

Closing this issue as it has been resolved in version 2.12.1 🎉
-> #112 (comment)

from terraform-aws-transit-gateway.

Confused this issue with the other one I've created. Sorry for any inconveniences.

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

Can confirm, I have the same issue.

from terraform-aws-transit-gateway.

I have the same issue.

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-transit-gateway.

"Keep alive" post

from terraform-aws-transit-gateway.

can confirm, also having this issue.

from terraform-aws-transit-gateway.

Same here, it does work when replacing the for_each statement with a count, but the trade-off isn't worth it in our opinion.

Really? My attempts to replace it with a count locally also fail with a similar error

│ Error: Invalid count argument
│
│   on ../../main.tf line 133, in resource "aws_route" "this":
│  133:   count = length(local.vpc_route_table_destination_cidr)
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict
│ how many instances will be created. To work around this, use the -target argument to first apply only the resources
│ that the count depends on.

from terraform-aws-transit-gateway.

Same here, it does work when replacing the for_each statement with a count, but the trade-off isn't worth it in our opinion.

Really? My attempts to replace it with a count locally also fail with a similar error

│ Error: Invalid count argument
│
│   on ../../main.tf line 133, in resource "aws_route" "this":
│  133:   count = length(local.vpc_route_table_destination_cidr)
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict
│ how many instances will be created. To work around this, use the -target argument to first apply only the resources
│ that the count depends on.

Interesting, might this be related to the tf version? I haven't tried this since August last year.

from terraform-aws-transit-gateway.