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
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
Expected behaviour is that 'azurerm_maintenance_assignment_virtual_machine' would notice that the VM is no longer there and would remove the attachment, instead of just updating the state and leaving attachment in the Azure portal.
Actual Behaviour
I provided a snippet of a module, which is for our patching solution. This module expects variable 'var.virtual_machines' - a list of vm ids. We have another module which creates VMs. When one of the vm is deleted, and the id of the vm is removed from the 'var.virtual_machines' variable, the attachment resource is not deleted. This creates a lot of manual work in the Azure portal.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Terraform Version
1.3.0
AzureRM Provider Version
3.107.0
Affected Resource(s)/Data Source(s)
azurerm_maintenance_assignment_virtual_machine
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Expected behaviour is that 'azurerm_maintenance_assignment_virtual_machine' would notice that the VM is no longer there and would remove the attachment, instead of just updating the state and leaving attachment in the Azure portal.
Actual Behaviour
I provided a snippet of a module, which is for our patching solution. This module expects variable 'var.virtual_machines' - a list of vm ids. We have another module which creates VMs. When one of the vm is deleted, and the id of the vm is removed from the 'var.virtual_machines' variable, the attachment resource is not deleted. This creates a lot of manual work in the Azure portal.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: