Skip to content
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

azurerm_[linux|windows]_virtual_machine: Allow to specify OS disk for import (and make OS disk id an output) #20343

Closed
1 task done
hofmannma opened this issue Feb 7, 2023 · 3 comments

Comments

@hofmannma
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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

azurerm_[linux|windows]_virtual_machine does not allow to specify OS disk for creation or import (after Azure site recovery).
The documentation says to use azurerm_virtual_machine instead. However this resource type is deprecated starting 3.x and there is no feature parity anymore.
So if you use a new 3.x feature and want to import a machine after ASR back into terraform it's broken. Cannot use terraform anymore.

New or Affected Resource(s)/Data Source(s)

azurerm_[linux|windows]_virtual_machine

Potential Terraform Configuration

No response

References

No response

@myc2h6o
Copy link
Contributor

myc2h6o commented Feb 8, 2023

Hi @hofmannma this looks same as the feature request #8195, would you mind subscribing to it for update.

@tombuildsstuff
Copy link
Contributor

hi @hofmannma

As @myc2h6o has mentioned, this has previously been requested in/is a duplicate of #8195, please subscribe to that issue for updates.

Thanks!

@tombuildsstuff tombuildsstuff closed this as not planned Won't fix, can't repro, duplicate, stale Feb 8, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants