Route Table Association

Terraform Providers Azure
1

When associating a route table with a Subnet, Terraform is repeatedly removing and re-adding it on subsequent deployments. Using v0.12

resource "azurerm_subnet_route_table_association" "east2rtsubnet" {
  provider       = "azurerm.local"
  subnet_id      = "${azurerm_subnet.vneteast-compute-subnet.id}"
  route_table_id = "${azurerm_route_table.rteast.id}"
}

resource "azurerm_subnet_route_table_association" "centralrtsubnet" {
  provider       = "azurerm.local"
  subnet_id      = "${azurerm_subnet.vnetcentral-compute-subnet.id}"
  route_table_id = "${azurerm_route_table.rtcentral.id}"
}
2

DIdn’t see this tidbit in documentation:

NOTE: Subnet <-> Route Table associations currently need to be configured on both this resource and using the route_table_id field on the azurerm_subnet resource. The next major version of the AzureRM Provider (2.0) will remove the route_table_id field from the azurerm_subnet resource such that this resource is used to link resources in future.