We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Current code for adding routes is based on count
count
terraform-aws-vpc-peering/main.tf
Lines 51 to 67 in 47c6e51
If matching pattern tag for a route is changed then only associated route table for this exact peering should be changed.
It's possible that downtime will happen during terraform apply when tags will be changed on route.
aws_route inside this module should use for_each which would prevent temporary routing changes
aws_route
for_each
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the Feature
Current code for adding routes is based on
count
terraform-aws-vpc-peering/main.tf
Lines 51 to 67 in 47c6e51
Changing tags can possible result in changing count order and removal of actually using peering routing.
Expected Behavior
If matching pattern tag for a route is changed then only associated route table for this exact peering should be changed.
Use Case
It's possible that downtime will happen during terraform apply when tags will be changed on route.
Describe Ideal Solution
aws_route
inside this module should usefor_each
which would prevent temporary routing changesThe text was updated successfully, but these errors were encountered: