-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Subnet used by destroyed azurerm_api_management cannot be deleted #1520
Comments
hey @torresdal Thanks for opening this issue / for PR #1516 Given this issue is in reference to a PR which hasn't been merged/shipped yet - I'm going to close it for the moment so that we can discuss this in #1516. The error being returned in this case is coming from the Azure API - where as you've identified the API Management instance still exists for a period of time once it's deleted; given this is a bug in the Azure SDK for Go - would you mind opening an issue on that repository where that can be fixed? Thanks! |
Will do! |
@torresdal @tombuildsstuff, this was closed but I think it should be reopened now to allow support for the |
@tharris29 Azure/azure-sdk-for-go#2199 and Azure/azure-rest-api-specs#4409 No activity or progress as far as I can see. |
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! |
Community Note
Terraform Version
Terraform v0.11.7
Affected Resource(s)
azurerm_api_management
#1516)Terraform Configuration Files
Debug Output
https://gist.github.com/torresdal/df34f85a8288d39fcc205c45c3d2914a
Panic Output
Expected Behavior
The resource
azurerm_subnet
should have been successfully destroyed and not being used byazurerm_api_management
anymore, sinceazurerm_api_management
have been destroyed.Actual Behavior
Note: Taking into account that it takes from 30-50 minutes to create a
api_management
resource in Azure and only seconds to delete it, it would be safe to assume that the actual underlying Azure resources are still being deleted behind the scenes, after the Delete call to the Azure API has succeeded. It would also be natural to assume that these resources are the ones preventingazurerm_subnet
to be deleted.Steps to Reproduce
terraform apply
terraform destroy
References
azurerm_api_management
#1516The text was updated successfully, but these errors were encountered: