Expose `os_disk.id` in `azurerm_linux_virtual_machine` and `azurerm_windows_virtual_machine`

[skgsergio]

Is there an existing issue for this?

• [X] I have searched the existing issues

Community Note

• Please vote on this issue by adding a :thumbsup: 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.

Description

In some scenarios like creating a azurerm_data_protection_backup_instance_disk is useful to have the azurerm_linux_virtual_machine.example.os_disk[0].id in order to avoid having to do the extra step of creating a data.azurerm_managed_disk.example_os_disk resource.

AFAIK in go-azure-sdk the ID is already present in OSDisk.ManagedDisk.Id.

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

azurerm_linux_virtual_machine, azurerm_windows_virtual_machine

Potential Terraform Configuration

No response

References

No response

[Chambras]

Interesting @skgsergio I will try to take a look

[jackofallops]

Interesting @skgsergio I will try to take a look

Thanks for the issue @skgsergio, and for the enthusiasm @Chambras. We're looking at this as part of a larger piece of work sometime after the release of 4.0. It looks like a simple thing on the surface, but we need to be mindful of a number of other related changes so we don't block those by implementing something too early. If we can ask that contributors don't try and tackle this one until we've had opportunity to review the whole task, that would be appreciated as we'd likely end up needing to close PR's, which we prefer not to have to do.

Thanks!

[Chambras]

Thanks for the background and explanation @jackofallops I totally understand!