Support for disk attachment to VMs at creation time
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!--- Thank you for keeping this note for the community ---> ### Description Azure [allows VMs to be booted with managed data disks pre-attached](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/tutorial-manage-disks#create-and-attach-disks)/attached-on-boot. This enables use cases where `cloud-init` and/or other "on-launch" configuration management tooling is able to prepare them for use as part of the initialisation process. This provider currently only supports this case for individual VMs with the older, deprecated `azurerm_virtual_machine` resource. The new `azurerm_linux_virtual_machine` and `azurerm_windows_virtual_machine` resources instead opt to push users towards the separate `azurerm_virtual_machine_data_disk_attachment` which only attaches data disks to an existing VM post-boot, which fails to service the use case laid out above. This is in contrast to the respective `*_scale_set` providers which (albeit out of necess
Posted by mal on Mar 15, 2020, 6:18 AM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Support for disk attachment to VMs at creation time
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!--- Thank you for keeping this note for the community ---> ### Description Azure [allows VMs to be booted with managed data disks pre-attached](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/tutorial-manage-disks#create-and-attach-disks)/attached-on-boot. This enables use cases where `cloud-init` and/or other "on-launch" configuration management tooling is able to prepare them for use as part of the initialisation process. This provider currently only supports this case for individual VMs with the older, deprecated `azurerm_virtual_machine` resource. The new `azurerm_linux_virtual_machine` and `azurerm_windows_virtual_machine` resources instead opt to push users towards the separate `azurerm_virtual_machine_data_disk_attachment` which only attaches data disks to an existing VM post-boot, which fails to service the use case laid out above. This is in contrast to the respective `*_scale_set` providers which (albeit out of necess
Comments (0)
No comments yet. Start the discussion.