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 "+1" or "me too" comments, 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
Description
In the previous azurerm_virtual_machine there was the capability to deploy a VM from an existing managed disk. (both a managed disk imported to the state or one that isn't)
However the new resources don't seem to support this. I'm unsure if that is intentional or not?
Taking a look through this appears to be a duplicate of #8195 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #8195 for updates?
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.
Community Note
Description
In the previous azurerm_virtual_machine there was the capability to deploy a VM from an existing managed disk. (both a managed disk imported to the state or one that isn't)
However the new resources don't seem to support this. I'm unsure if that is intentional or not?
New or Affected Resource(s)
Previous Terraform Configuration
The text was updated successfully, but these errors were encountered: