Skip to content
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

azurerm_route does not delete routes associated with the table when removed #11747

Closed
geofffranks opened this issue Feb 7, 2017 · 2 comments
Closed

Comments

@geofffranks
Copy link

Terraform Version

Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.

terraform v0.8.5

Affected Resource(s)

Please list the resources as a list, for example:

  • awsrm_route

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

resource "azurerm_route_table" "external" {
    name = "${var.resource_group_name}-external"
    location = "${var.azure_region}"
    resource_group_name = "${azurerm_resource_group.default.name}"

    route {
        name = "internet"
        address_prefix = "0.0.0.0/0"
        next_hop_type = "internet"
    }
}

Expected Behavior

When removing the route from the above definition, terraform should remove the route from the routing table in Azure.

Actual Behavior

Terraform says nothing will change during plan or apply phases

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. Deploy above route table in sample config
  2. Delete the route from the config
  3. terraform plan + apply
@rrudduck
Copy link
Contributor

rrudduck commented Feb 8, 2017

I'm wondering if this has something to do with the route type. I added an acceptance test that verifies removal of a route (going from 2 to 1) in the config does in fact remove the route. I'll try checking your specific example.

@ghost
Copy link

ghost commented Apr 10, 2020

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 ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants