so

VirtualMachine

implicitly creates reasources that pulumi doesn't track--disks and network interfaces and such. I noticed that the random ID logic isn't used with them. How are people working with this? Explicitly randomizing them? Explicitly tracking them as pulumi resources? just kinda shrugging?

I haven't created a VM in Azure yet with Pulumi so not sure this will work. Can you create those resources (disk, network interface, etc) with Pulumi and link them to the virtual machine?

That's what I mean by "explicitly tracking them"--rewriting the code so that they're pulumi resources instead of implied

Sorry, I misunderstood. The documentation examples show some example of linking to existing resources. The first one shows linking to an existing network interface. I assume the other examples show everything else. I have a project coming up where I will be creating VMs and just assumed the code would have to explicitly create all resources. https://www.pulumi.com/registry/packages/azure-native/api-docs/compute/virtualmachine/

https://github.com/pulumi/templates/blob/81c76b93d3966b14c5e953cee4dfcc1472f21ce5/vm-azure-python/__main__.py#L152-L155 this creates a resource not visible to pulumi

Sorry I don't have any example code. It looks like setting the OS disk can be linked to some other resource. It has the VHD property which I think is just the URI to the disk.

... yes, which is one of the solutions I mentioned in my original message.

Oh, I'm so sorry. I really misunderstood your question.

I do have one reason to explicitly manage disks through pulumi: You can only resize disks on the disk resource (not on the VM)