You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is problematic when using terragrunt run-all to set up an entire stack (vpc + client vpn etc.) as the plan will fail since the VPC doesn't exist yet:
│ Error: no matching EC2 VPC found
│
│ with module.vpn.data.aws_vpc.this,
│ on .terraform/modules/vpn/main.tf line 42, in data "aws_vpc""this":
│ 42: data "aws_vpc""this" {
│
I assume this would also happen when running normal terraform plan (without terragrunt) with vpc + client vpn in the same main.tf, but I didn't test it.
The solution is to remove the VPC data resource and add a new variable endpoint_vpc_cidr_block.
Will be happy to contribute a PR.
The text was updated successfully, but these errors were encountered:
Hi,
Currently, the VPC CIDR block is pulled from the VPC data:
terraform-aws-client-vpn-endpoint/main.tf
Lines 42 to 44 in 35e1693
This is problematic when using
terragrunt run-all
to set up an entire stack (vpc + client vpn etc.) as the plan will fail since the VPC doesn't exist yet:I assume this would also happen when running normal terraform plan (without terragrunt) with vpc + client vpn in the same main.tf, but I didn't test it.
The solution is to remove the VPC data resource and add a new variable
endpoint_vpc_cidr_block
.Will be happy to contribute a PR.
The text was updated successfully, but these errors were encountered: