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
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.
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.
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
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:
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
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:
The text was updated successfully, but these errors were encountered: