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'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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 5, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Today, we cannot associate an azurerm_route_table to an azurerm_subnet in terraform for a resource created by another terraform module.
It is possible to associate routes within AWS using route_table_association: https://www.terraform.io/docs/providers/aws/r/route_table_association.html
For Azure we need one as well.
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
It would have associated the terraform the azurerm_route_table with the azurerm_subnet.
Actual Behavior
This resource doesn't exist
Steps to Reproduce
terraform apply
Important Factoids
References
#1337 - broken data azurerm_subnet route_table_id: not functioning
The text was updated successfully, but these errors were encountered: