Hi All,
I am seeing strange behavior when adding a vpc peering route to Aws route table. The route last route is getting recreated for no reason. Similar issues is found when modifying security group as well. Should we run this in a specific order ?. Anyone experienced similar issue?.
~ resource "aws_route_table" "private_route_table" {
id = "rtb-9uh98y0ijoug979"
~ route = [
- {
- carrier_gateway_id = ""
- cidr_block = "1.1.1.1.1/16"
- core_network_arn = ""
- destination_prefix_list_id = ""
- egress_only_gateway_id = ""
- gateway_id = ""
- instance_id = ""
- ipv6_cidr_block = ""
- local_gateway_id = ""
- nat_gateway_id = "nat-ouh897gt87g9uoiuh9"
- network_interface_id = ""
- transit_gateway_id = ""
- vpc_endpoint_id = ""
- vpc_peering_connection_id = ""
},
+ {
+ carrier_gateway_id = ""
+ cidr_block = "0.0.0.0/16"
+ core_network_arn = ""
+ destination_prefix_list_id = ""
+ egress_only_gateway_id = ""
+ gateway_id = ""
+ instance_id = ""
+ ipv6_cidr_block = ""
+ local_gateway_id = ""
+ nat_gateway_id = ""
+ network_interface_id = ""
+ transit_gateway_id = ""
+ vpc_endpoint_id = ""
+ vpc_peering_connection_id = "pcx-iubh8yf686fg9uh9"
},
+ {
+ carrier_gateway_id = null
+ cidr_block = "1.1.1.1.1/16"
+ core_network_arn = null
+ destination_prefix_list_id = null
+ egress_only_gateway_id = null
+ gateway_id = null
+ instance_id = null
+ ipv6_cidr_block = null
+ local_gateway_id = null
+ nat_gateway_id = "nat-ouh897gt87g9uoiuh9"
+ network_interface_id = null
+ transit_gateway_id = null
+ vpc_endpoint_id = null
+ vpc_peering_connection_id = null
},
]