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
First of all I'm not sure if it is a real bug or not :)
I faced with the behaviour which does not seem proper, so I have implemented some fix in my fork of the module, but I would like to discuss it here and could provide a pull request for that.
When we execute this module and provide there, let's say, 3 public and 3 private subnets, and after that pass the following parameters
enable_nat_gateway = true
single_nat_gateway = true
enable_vpn_gateway = true
the module suggest to create multiple aws_vpn_gateway_route_propagation.private resources with route_table_id and vpn_gateway_id have exactly the same content.
This seems strange because then we have one resource in AWS managed by multiple terraform resources.
The workaround which I have implemented if just to use an additional bool parameter, like single_vgw_route_propagation_private and then use it like
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
This is also a problem for intra subnets, where there is always only one route table. The module should create one aws_vpn_gateway_route_propagation per route table rather than one per subnet. This is a bug, and the only reason it doesn't fail fatally is because of the wrap-around behaviour of element().
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
Description
First of all I'm not sure if it is a real bug or not :)
I faced with the behaviour which does not seem proper, so I have implemented some fix in my fork of the module, but I would like to discuss it here and could provide a pull request for that.
When we execute this module and provide there, let's say, 3 public and 3 private subnets, and after that pass the following parameters
the module suggest to create multiple aws_vpn_gateway_route_propagation.private resources with route_table_id and vpn_gateway_id have exactly the same content.
This seems strange because then we have one resource in AWS managed by multiple terraform resources.
The workaround which I have implemented if just to use an additional bool parameter, like single_vgw_route_propagation_private and then use it like
The text was updated successfully, but these errors were encountered: