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
Thanks for opening this issue. Seems terraform doesn't detect the change since there is computed attribute on properties "endpoint" and "route". So I made a fix for it.
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!
ghost
locked and limited conversation to collaborators
Sep 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.12.9
Affected Resource(s)
azurerm_iothub
Terraform Configuration Files
followed by:
Debug Output
N/A
Panic Output
Expected Behavior
Expected IoT hub created with endpoint and route. Followed by the next run removing the endpoint and route
Actual Behavior
Terraform did not detect any changes on the second run, and left existing route/endpoint in place
Steps to Reproduce
terraform apply
first blockterraform apply
second blockImportant Factoids
This appears to be the case across all endpoint and route types event hub, service bus, etc.
References
The text was updated successfully, but these errors were encountered: