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
I am expecting that I should be able to add multiple entries of static routes to terraform resource aws_vpn_connection_route. However, the destination_cidr_block doesn't allow to add a list and expects a single value ( as also seen in the screenshot during the terraform plan) Actual:
resource "aws_vpn_connection_route" "office" { destination_cidr_block = "10.0.0.0/16"
vpn_connection_id = "${aws_vpn_connection.main.id}"
}
This issue has been automatically migrated to hashicorp/terraform-provider-aws#1324 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 8, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am expecting that I should be able to add multiple entries of static routes to terraform resource aws_vpn_connection_route. However, the destination_cidr_block doesn't allow to add a list and expects a single value ( as also seen in the screenshot during the terraform plan)
Actual:
resource "aws_vpn_connection_route" "office" {
destination_cidr_block = "10.0.0.0/16"
vpn_connection_id = "${aws_vpn_connection.main.id}"
}
Expectation:
resource "aws_vpn_connection_route" "office" {
destination_cidr_block = ["10.0.0.0/16","10.2.0.0/16"]
vpn_connection_id = "${aws_vpn_connection.main.id}"
}
I should be able to add multiple routes as this is doable through the AWS console ( seen below)
The text was updated successfully, but these errors were encountered: