-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_vpn_gateway_route_propagation creates #977
Comments
This issue has been automatically marked as stale because it has been open 30 days |
Any thoughts? |
This is also a problem for intra subnets, where there is always only one route table. The module should create one |
This issue has been automatically marked as stale because it has been open 30 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: