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
* Resolved merge conflicts
* Changes conforming to HashiCorp guidelines and additional bug fixes
* Rebase merge
* Rebase merge
* Merging changes
* Changes to tests and code constructs
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
terraform version
0.8.4
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Updating the route table should keep or update the subnet association of the table.
Actual Behavior
The initial
terraform apply
will create all the resources without an issue.When updating the route table (by updating the tags for instance), the subnet association is dropped.
Steps to Reproduce
terraform apply
a route table with at least one route.terraform apply
will update the tags, but remove the subnet association from the route table.The text was updated successfully, but these errors were encountered: