Vsphere Docs: No import sections are provided.

[MitchellGerdisch]

What happened?

Other providers include a pulumi import section for each resource.
The vSphere docs are missing this.

It's not intuitively obvious what the resource type is (appears to be of the form vsphere:index/ResourceType:resourcetype
and it's not clear what correct vsphere IDs look like.

So having this documentation would be very helpful.

Expected Behavior

Have import sections for he resources.

Steps to reproduce

Go to the vsphere provider docs and pick a resource, e.g. https://www.pulumi.com/registry/packages/vsphere/api-docs/virtualmachine/

Look for an import section like seen else where (e.g. https://www.pulumi.com/registry/packages/aws/api-docs/iot/thing/#import).

Output of pulumi about

N/A

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[MitchellGerdisch]

FYI: Import for VM looks like:

pulumi import vsphere:index/virtualMachine:VirtualMachine name /DATACENTER/RESOURCEPOOL/vm/VMNAME

Fixed typo as per @JCBlouin comment below.

[iwahbe]

Thanks @MitchellGerdisch. We have added this to our docs quality epic.

[JCBlouin]

Any progress on this? I want to bring our VMWare environment under Pulumi control but not being able to import existing resources is hampering that effort.
The command @MitchellGerdisch kindly provided isn't working for me. When I try that I get "error: Preview failed: unrecognized resource type (Read): vsphere:index/virtualmachine:VirtualMachine"

[JCBlouin]

Ah, I found the problem with the command @MitchellGerdisch posted - it needs to be:
vsphere:index/virtualMachine:VirtualMachine

I figured that out by creating a test VM and looking at the resulting URN in Pulumi.
I can do that for other resources but I don't think I'd ever have figured out the ID format.
Also, I'd prefer not to have to do all this by guessing/trial and error.

[MitchellGerdisch]

@JCBlouin Sorry about the typo and thanks for providing the corrected version.
I'll edit my original comment accordingly.

[evilhamsterman]

Another thing is importing resources that require information about other resources. Like trying to import a Distributed Virtual Switch requires providing a datacenter

pulumi import vsphere:index/distributedVirtualSwitch:DistributedVirtualSwitch dvs VmwareDistributedVirtualSwitch-dvs-62
Previewing import (dev):
     Type                                       Name     Plan       Info
     pulumi:pulumi:Stack                        it-dev              1 error
 =   └─ vsphere:index:DistributedVirtualSwitch  dvs  import     1 error

Diagnostics:
  vsphere:index:DistributedVirtualSwitch (dvs-csq):
    error: Preview failed: importing VmwareDistributedVirtualSwitch-dvs-62: error locating DVS: please specify a datacenter

  pulumi:pulumi:Stack (it-dev):
    error: preview failed

The ID for each resource is different too. Some take a UID, some a folder location.

[iwahbe]

I suspect that this will be fixed by #597. I'll add needs-triage as a reminder to check after vsphere has been published with new docs.