pulumi-vsphere 4.12.0a1727221820__py3-none-any.whl → 4.12.0a1727889180__py3-none-any.whl

pulumi_vsphere/vapp_entity.py

@@ -406,7 +406,77 @@ class VappEntity(pulumi.CustomResource):
                  wait_for_guest: Optional[pulumi.Input[bool]] = None,
                  __props__=None):
         """
-        Create a VappEntity resource with the given unique name, props, and options.
+        The `VappEntity` resource can be used to describe the behavior of an
+        entity (virtual machine or sub-vApp container) in a vApp container.
+
+        For more information on vSphere vApps, see [this
+        page][ref-vsphere-vapp].
+
+        [ref-vsphere-vapp]: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vm-administration/GUID-2A95EBB8-1779-40FA-B4FB-4D0845750879.html
+
+        ## Example Usage
+
+        The basic example below sets up a vApp container and a virtual machine in a
+        compute cluster and then creates a vApp entity to change the virtual machine's
+        power on behavior in the vApp container.
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        config = pulumi.Config()
+        datacenter = config.get("datacenter")
+        if datacenter is None:
+            datacenter = "dc-01"
+        cluster = config.get("cluster")
+        if cluster is None:
+            cluster = "cluster-01"
+        datacenter_get_datacenter = vsphere.get_datacenter(name=datacenter)
+        compute_cluster = vsphere.get_compute_cluster(name=cluster,
+            datacenter_id=datacenter_get_datacenter.id)
+        network = vsphere.get_network(name="network1",
+            datacenter_id=datacenter_get_datacenter.id)
+        datastore = vsphere.get_datastore(name="datastore1",
+            datacenter_id=datacenter_get_datacenter.id)
+        vapp_container = vsphere.VappContainer("vapp_container",
+            name="vapp-container-test",
+            parent_resource_pool_id=compute_cluster.id)
+        vm = vsphere.VirtualMachine("vm",
+            name="virtual-machine-test",
+            resource_pool_id=vapp_container.id,
+            datastore_id=datastore.id,
+            num_cpus=2,
+            memory=1024,
+            guest_id="ubuntu64Guest",
+            disks=[{
+                "label": "disk0",
+                "size": 1,
+            }],
+            network_interfaces=[{
+                "network_id": network.id,
+            }])
+        vapp_entity = vsphere.VappEntity("vapp_entity",
+            target_id=vm.moid,
+            container_id=vapp_container.id,
+            start_action="none")
+        ```
+
+        ## Import
+
+        An existing vApp entity can be imported into this resource via
+
+        the ID of the vApp Entity.
+
+        ```sh
+        $ pulumi import vsphere:index/vappEntity:VappEntity vapp_entity vm-123:res-456
+        ```
+
+        The above would import the vApp entity that governs the behavior of the virtual
+
+        machine with a [managed object ID][docs-about-morefs] of vm-123 in the vApp
+
+        container with the [managed object ID][docs-about-morefs] res-456.
+
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] container_id: Managed object ID of the vApp
@@ -438,7 +508,77 @@ class VappEntity(pulumi.CustomResource):
                  args: VappEntityArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Create a VappEntity resource with the given unique name, props, and options.
+        The `VappEntity` resource can be used to describe the behavior of an
+        entity (virtual machine or sub-vApp container) in a vApp container.
+
+        For more information on vSphere vApps, see [this
+        page][ref-vsphere-vapp].
+
+        [ref-vsphere-vapp]: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vm-administration/GUID-2A95EBB8-1779-40FA-B4FB-4D0845750879.html
+
+        ## Example Usage
+
+        The basic example below sets up a vApp container and a virtual machine in a
+        compute cluster and then creates a vApp entity to change the virtual machine's
+        power on behavior in the vApp container.
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        config = pulumi.Config()
+        datacenter = config.get("datacenter")
+        if datacenter is None:
+            datacenter = "dc-01"
+        cluster = config.get("cluster")
+        if cluster is None:
+            cluster = "cluster-01"
+        datacenter_get_datacenter = vsphere.get_datacenter(name=datacenter)
+        compute_cluster = vsphere.get_compute_cluster(name=cluster,
+            datacenter_id=datacenter_get_datacenter.id)
+        network = vsphere.get_network(name="network1",
+            datacenter_id=datacenter_get_datacenter.id)
+        datastore = vsphere.get_datastore(name="datastore1",
+            datacenter_id=datacenter_get_datacenter.id)
+        vapp_container = vsphere.VappContainer("vapp_container",
+            name="vapp-container-test",
+            parent_resource_pool_id=compute_cluster.id)
+        vm = vsphere.VirtualMachine("vm",
+            name="virtual-machine-test",
+            resource_pool_id=vapp_container.id,
+            datastore_id=datastore.id,
+            num_cpus=2,
+            memory=1024,
+            guest_id="ubuntu64Guest",
+            disks=[{
+                "label": "disk0",
+                "size": 1,
+            }],
+            network_interfaces=[{
+                "network_id": network.id,
+            }])
+        vapp_entity = vsphere.VappEntity("vapp_entity",
+            target_id=vm.moid,
+            container_id=vapp_container.id,
+            start_action="none")
+        ```
+
+        ## Import
+
+        An existing vApp entity can be imported into this resource via
+
+        the ID of the vApp Entity.
+
+        ```sh
+        $ pulumi import vsphere:index/vappEntity:VappEntity vapp_entity vm-123:res-456
+        ```
+
+        The above would import the vApp entity that governs the behavior of the virtual
+
+        machine with a [managed object ID][docs-about-morefs] of vm-123 in the vApp
+
+        container with the [managed object ID][docs-about-morefs] res-456.
+
         :param str resource_name: The name of the resource.
         :param VappEntityArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.

pulumi_vsphere/virtual_disk.py

@@ -370,7 +370,44 @@ class VirtualDisk(pulumi.CustomResource):
                  vmdk_path: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        Create a VirtualDisk resource with the given unique name, props, and options.
+        The `VirtualDisk` resource can be used to create virtual disks outside
+        of any given `VirtualMachine`
+        resource. These disks can be attached to a virtual machine by creating a disk
+        block with the `attach` parameter.
+
+        ## Example Usage
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        datastore = vsphere.get_datacenter(name="datastore-01")
+        virtual_disk = vsphere.VirtualDisk("virtual_disk",
+            size=40,
+            type="thin",
+            vmdk_path="/foo/foo.vmdk",
+            create_directories=True,
+            datacenter=datacenter.name,
+            datastore=datastore_vsphere_datastore["name"])
+        ```
+
+        ## Import
+
+        An existing virtual disk can be imported into this resource
+
+        via supplying the full datastore path to the virtual disk. An example is below:
+
+        ```sh
+        $ pulumi import vsphere:index/virtualDisk:VirtualDisk virtual_disk \\
+        ```
+
+          '{"virtual_disk_path": "/dc-01/[datastore-01]foo/bar.vmdk", \\ "create_directories": "true"}'
+
+        The above would import the virtual disk located at `foo/bar.vmdk` in the `datastore-01`
+
+        datastore of the `dc-01` datacenter with `create_directories` set as `true`.
+
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] adapter_type: The adapter type for this virtual disk. Can be
@@ -413,7 +450,44 @@ class VirtualDisk(pulumi.CustomResource):
                  args: VirtualDiskArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Create a VirtualDisk resource with the given unique name, props, and options.
+        The `VirtualDisk` resource can be used to create virtual disks outside
+        of any given `VirtualMachine`
+        resource. These disks can be attached to a virtual machine by creating a disk
+        block with the `attach` parameter.
+
+        ## Example Usage
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        datastore = vsphere.get_datacenter(name="datastore-01")
+        virtual_disk = vsphere.VirtualDisk("virtual_disk",
+            size=40,
+            type="thin",
+            vmdk_path="/foo/foo.vmdk",
+            create_directories=True,
+            datacenter=datacenter.name,
+            datastore=datastore_vsphere_datastore["name"])
+        ```
+
+        ## Import
+
+        An existing virtual disk can be imported into this resource
+
+        via supplying the full datastore path to the virtual disk. An example is below:
+
+        ```sh
+        $ pulumi import vsphere:index/virtualDisk:VirtualDisk virtual_disk \\
+        ```
+
+          '{"virtual_disk_path": "/dc-01/[datastore-01]foo/bar.vmdk", \\ "create_directories": "true"}'
+
+        The above would import the virtual disk located at `foo/bar.vmdk` in the `datastore-01`
+
+        datastore of the `dc-01` datacenter with `create_directories` set as `true`.
+
         :param str resource_name: The name of the resource.
         :param VirtualDiskArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.

pulumi_vsphere/virtual_machine.py

@@ -2718,7 +2718,30 @@ class VirtualMachine(pulumi.CustomResource):
                  wait_for_guest_net_timeout: Optional[pulumi.Input[int]] = None,
                  __props__=None):
         """
-        Create a VirtualMachine resource with the given unique name, props, and options.
+        ## Import
+
+        ### Additional Importing Requirements
+
+        Many of the requirements for [cloning](#additional-requirements-and-notes-for-cloning) apply to importing. Although importing writes directly to the Terraform state, some rules can not be enforced during import time, so every effort should be made to ensure the correctness of the configuration before the import.
+
+        The following requirements apply to import:
+
+        * The disks must have a [`label`](#label) argument assigned in a convention matching `diskN`, starting with disk number 0, based on each virtual disk order on the SCSI bus. As an example, a disk on SCSI controller `0` with a unit number of `0` would be labeled as `disk0`, a disk on the same controller with a unit number of `1` would be `disk1`, but the next disk, which is on SCSI controller `1` with a unit number of `0`, still becomes `disk2`.
+
+        * Disks are always imported with [`keep_on_remove`](#keep_on_remove) enabled until the first `pulumi up` run which will remove the setting for known disks. This process safeguards against naming or accounting mistakes in the disk configuration.
+
+        * The storage controller count for the resource is set to the number of contiguous storage controllers found, starting with the controller at SCSI bus number `0`. If no storage controllers are discovered, the virtual machine is not eligible for import. For maximum compatibility, ensure that the virtual machine has the exact number of storage controllers needed and set the storage controller count accordingly.
+
+        After importing, you should run `pulumi preview`. Unless you have changed anything else in the configuration that would cause other attributes to change. The only difference should be configuration-only changes, which are typically comprised of:
+
+        * The [`imported`](#imported) flag will transition from `true` to `false`.
+
+        * The [`keep_on_remove`](#keep_on_remove) of known disks will transition from `true` to `false`.
+
+        * Configuration supplied in the [`clone`](#clone) block, if present, will be persisted to state. This initial persistence operation does not perform any cloning or customization actions, nor does it force a new resource. After the first apply operation, further changes to `clone` will force the creation of a new resource.
+
+        These changes only update Terraform state when applied. Hence, it is safe to run when the virtual machine is running. If more settings are modified, you may need to plan maintenance accordingly for any necessary virtual machine re-configurations.
+
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] alternate_guest_name: The guest name for the operating system when guest_id is otherGuest or otherGuest64.
@@ -2816,7 +2839,30 @@ class VirtualMachine(pulumi.CustomResource):
                  args: VirtualMachineArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Create a VirtualMachine resource with the given unique name, props, and options.
+        ## Import
+
+        ### Additional Importing Requirements
+
+        Many of the requirements for [cloning](#additional-requirements-and-notes-for-cloning) apply to importing. Although importing writes directly to the Terraform state, some rules can not be enforced during import time, so every effort should be made to ensure the correctness of the configuration before the import.
+
+        The following requirements apply to import:
+
+        * The disks must have a [`label`](#label) argument assigned in a convention matching `diskN`, starting with disk number 0, based on each virtual disk order on the SCSI bus. As an example, a disk on SCSI controller `0` with a unit number of `0` would be labeled as `disk0`, a disk on the same controller with a unit number of `1` would be `disk1`, but the next disk, which is on SCSI controller `1` with a unit number of `0`, still becomes `disk2`.
+
+        * Disks are always imported with [`keep_on_remove`](#keep_on_remove) enabled until the first `pulumi up` run which will remove the setting for known disks. This process safeguards against naming or accounting mistakes in the disk configuration.
+
+        * The storage controller count for the resource is set to the number of contiguous storage controllers found, starting with the controller at SCSI bus number `0`. If no storage controllers are discovered, the virtual machine is not eligible for import. For maximum compatibility, ensure that the virtual machine has the exact number of storage controllers needed and set the storage controller count accordingly.
+
+        After importing, you should run `pulumi preview`. Unless you have changed anything else in the configuration that would cause other attributes to change. The only difference should be configuration-only changes, which are typically comprised of:
+
+        * The [`imported`](#imported) flag will transition from `true` to `false`.
+
+        * The [`keep_on_remove`](#keep_on_remove) of known disks will transition from `true` to `false`.
+
+        * Configuration supplied in the [`clone`](#clone) block, if present, will be persisted to state. This initial persistence operation does not perform any cloning or customization actions, nor does it force a new resource. After the first apply operation, further changes to `clone` will force the creation of a new resource.
+
+        These changes only update Terraform state when applied. Hence, it is safe to run when the virtual machine is running. If more settings are modified, you may need to plan maintenance accordingly for any necessary virtual machine re-configurations.
+
         :param str resource_name: The name of the resource.
         :param VirtualMachineArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.

pulumi_vsphere/vmfs_datastore.py

@@ -461,7 +461,139 @@ class VmfsDatastore(pulumi.CustomResource):
                  tags: Optional[pulumi.Input[Sequence[pulumi.Input[str]]]] = None,
                  __props__=None):
         """
-        Create a VmfsDatastore resource with the given unique name, props, and options.
+        The `VmfsDatastore` resource can be used to create and manage VMFS
+        datastores on an ESXi host or a set of hosts. The resource supports using any
+        SCSI device that can generally be used in a datastore, such as local disks, or
+        disks presented to a host or multiple hosts over Fibre Channel or iSCSI.
+        Devices can be specified manually, or discovered using the
+        [`get_vmfs_disks`][data-source-vmfs-disks] data source.
+
+        [data-source-vmfs-disks]: /docs/providers/vsphere/d/vmfs_disks.html
+
+        ## Auto-Mounting of Datastores Within vCenter
+
+        Note that the current behavior of this resource will auto-mount any created
+        datastores to any other host within vCenter that has access to the same disk.
+
+        Example: You want to create a datastore with a iSCSI LUN that is visible on 3
+        hosts in a single vSphere cluster (`esxi1`, `esxi2` and `esxi3`). When you
+        create the datastore on `esxi1`, the datastore will be automatically mounted on
+        `esxi2` and `esxi3`, without the need to configure the resource on either of
+        those two hosts.
+
+        Future versions of this resource may allow you to control the hosts that a
+        datastore is mounted to, but currently, this automatic behavior cannot be
+        changed, so keep this in mind when writing your configurations and deploying
+        your disks.
+
+        ## Increasing Datastore Size
+
+        To increase the size of a datastore, you must add additional disks to the
+        `disks` attribute. Expanding the size of a datastore by increasing the size of
+        an already provisioned disk is currently not supported (but may be in future
+        versions of this resource).
+
+        > **NOTE:** You cannot decrease the size of a datastore. If the resource
+        detects disks removed from the configuration, the provider will give an error.
+
+        [cmd-taint]: /docs/commands/taint.html
+
+        ## Example Usage
+
+        ### Addition of local disks on a single host
+
+        The following example uses the default datacenter and default host to add a
+        datastore with local disks to a single ESXi server.
+
+        > **NOTE:** There are some situations where datastore creation will not work
+        when working through vCenter (usually when trying to create a datastore on a
+        single host with local disks). If you experience trouble creating the datastore
+        you need through vCenter, break the datastore off into a different configuration
+        and deploy it using the ESXi server as the provider endpoint, using a similar
+        configuration to what is below.
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        datacenter = vsphere.get_datacenter()
+        host = vsphere.get_host(datacenter_id=datacenter.id)
+        datastore = vsphere.VmfsDatastore("datastore",
+            name="test",
+            host_system_id=esxi_host["id"],
+            disks=[
+                "mpx.vmhba1:C0:T1:L0",
+                "mpx.vmhba1:C0:T2:L0",
+                "mpx.vmhba1:C0:T2:L0",
+            ])
+        ```
+
+        ### Auto-detection of disks via `get_vmfs_disks`
+
+        The following example makes use of the
+        `get_vmfs_disks` data source to auto-detect
+        exported iSCSI LUNS matching a certain NAA vendor ID (in this case, LUNs
+        exported from a [NetApp][ext-netapp]). These discovered disks are then loaded
+        into `VmfsDatastore`. The datastore is also placed in the
+        `datastore-folder` folder afterwards.
+
+        [ext-netapp]: https://kb.netapp.com/support/s/article/ka31A0000000rLRQAY/how-to-match-a-lun-s-naa-number-to-its-serial-number?language=en_US
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        host = vsphere.get_host(name="esxi-01.example.com",
+            datacenter_id=datacenter.id)
+        available = vsphere.get_vmfs_disks(host_system_id=host.id,
+            rescan=True,
+            filter="naa.60a98000")
+        datastore = vsphere.VmfsDatastore("datastore",
+            name="test",
+            host_system_id=esxi_host["id"],
+            folder="datastore-folder",
+            disks=[available.disks])
+        ```
+
+        ## Import
+
+        An existing VMFS datastore can be imported into this resource
+
+        via its managed object ID, via the command below. You also need the host system
+
+        ID.
+
+        ```sh
+        $ pulumi import vsphere:index/vmfsDatastore:VmfsDatastore datastore datastore-123:host-10
+        ```
+
+        You need a tool like [`govc`][ext-govc] that can display managed object IDs.
+
+        [ext-govc]: https://github.com/vmware/govmomi/tree/master/govc
+
+        In the case of govc, you can locate a managed object ID from an inventory path
+
+        by doing the following:
+
+        $ govc ls -i /dc/datastore/terraform-test
+
+        Datastore:datastore-123
+
+        To locate host IDs, it might be a good idea to supply the `-l` flag as well so
+
+        that you can line up the names with the IDs:
+
+        $ govc ls -l -i /dc/host/cluster1
+
+        ResourcePool:resgroup-10 /dc/host/cluster1/Resources
+
+        HostSystem:host-10 /dc/host/cluster1/esxi1
+
+        HostSystem:host-11 /dc/host/cluster1/esxi2
+
+        HostSystem:host-12 /dc/host/cluster1/esxi3
+
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[Mapping[str, pulumi.Input[str]]] custom_attributes: Map of custom attribute ids to attribute 
@@ -499,7 +631,139 @@ class VmfsDatastore(pulumi.CustomResource):
                  args: VmfsDatastoreArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Create a VmfsDatastore resource with the given unique name, props, and options.
+        The `VmfsDatastore` resource can be used to create and manage VMFS
+        datastores on an ESXi host or a set of hosts. The resource supports using any
+        SCSI device that can generally be used in a datastore, such as local disks, or
+        disks presented to a host or multiple hosts over Fibre Channel or iSCSI.
+        Devices can be specified manually, or discovered using the
+        [`get_vmfs_disks`][data-source-vmfs-disks] data source.
+
+        [data-source-vmfs-disks]: /docs/providers/vsphere/d/vmfs_disks.html
+
+        ## Auto-Mounting of Datastores Within vCenter
+
+        Note that the current behavior of this resource will auto-mount any created
+        datastores to any other host within vCenter that has access to the same disk.
+
+        Example: You want to create a datastore with a iSCSI LUN that is visible on 3
+        hosts in a single vSphere cluster (`esxi1`, `esxi2` and `esxi3`). When you
+        create the datastore on `esxi1`, the datastore will be automatically mounted on
+        `esxi2` and `esxi3`, without the need to configure the resource on either of
+        those two hosts.
+
+        Future versions of this resource may allow you to control the hosts that a
+        datastore is mounted to, but currently, this automatic behavior cannot be
+        changed, so keep this in mind when writing your configurations and deploying
+        your disks.
+
+        ## Increasing Datastore Size
+
+        To increase the size of a datastore, you must add additional disks to the
+        `disks` attribute. Expanding the size of a datastore by increasing the size of
+        an already provisioned disk is currently not supported (but may be in future
+        versions of this resource).
+
+        > **NOTE:** You cannot decrease the size of a datastore. If the resource
+        detects disks removed from the configuration, the provider will give an error.
+
+        [cmd-taint]: /docs/commands/taint.html
+
+        ## Example Usage
+
+        ### Addition of local disks on a single host
+
+        The following example uses the default datacenter and default host to add a
+        datastore with local disks to a single ESXi server.
+
+        > **NOTE:** There are some situations where datastore creation will not work
+        when working through vCenter (usually when trying to create a datastore on a
+        single host with local disks). If you experience trouble creating the datastore
+        you need through vCenter, break the datastore off into a different configuration
+        and deploy it using the ESXi server as the provider endpoint, using a similar
+        configuration to what is below.
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        datacenter = vsphere.get_datacenter()
+        host = vsphere.get_host(datacenter_id=datacenter.id)
+        datastore = vsphere.VmfsDatastore("datastore",
+            name="test",
+            host_system_id=esxi_host["id"],
+            disks=[
+                "mpx.vmhba1:C0:T1:L0",
+                "mpx.vmhba1:C0:T2:L0",
+                "mpx.vmhba1:C0:T2:L0",
+            ])
+        ```
+
+        ### Auto-detection of disks via `get_vmfs_disks`
+
+        The following example makes use of the
+        `get_vmfs_disks` data source to auto-detect
+        exported iSCSI LUNS matching a certain NAA vendor ID (in this case, LUNs
+        exported from a [NetApp][ext-netapp]). These discovered disks are then loaded
+        into `VmfsDatastore`. The datastore is also placed in the
+        `datastore-folder` folder afterwards.
+
+        [ext-netapp]: https://kb.netapp.com/support/s/article/ka31A0000000rLRQAY/how-to-match-a-lun-s-naa-number-to-its-serial-number?language=en_US
+
+        ```python
+        import pulumi
+        import pulumi_vsphere as vsphere
+
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        host = vsphere.get_host(name="esxi-01.example.com",
+            datacenter_id=datacenter.id)
+        available = vsphere.get_vmfs_disks(host_system_id=host.id,
+            rescan=True,
+            filter="naa.60a98000")
+        datastore = vsphere.VmfsDatastore("datastore",
+            name="test",
+            host_system_id=esxi_host["id"],
+            folder="datastore-folder",
+            disks=[available.disks])
+        ```
+
+        ## Import
+
+        An existing VMFS datastore can be imported into this resource
+
+        via its managed object ID, via the command below. You also need the host system
+
+        ID.
+
+        ```sh
+        $ pulumi import vsphere:index/vmfsDatastore:VmfsDatastore datastore datastore-123:host-10
+        ```
+
+        You need a tool like [`govc`][ext-govc] that can display managed object IDs.
+
+        [ext-govc]: https://github.com/vmware/govmomi/tree/master/govc
+
+        In the case of govc, you can locate a managed object ID from an inventory path
+
+        by doing the following:
+
+        $ govc ls -i /dc/datastore/terraform-test
+
+        Datastore:datastore-123
+
+        To locate host IDs, it might be a good idea to supply the `-l` flag as well so
+
+        that you can line up the names with the IDs:
+
+        $ govc ls -l -i /dc/host/cluster1
+
+        ResourcePool:resgroup-10 /dc/host/cluster1/Resources
+
+        HostSystem:host-10 /dc/host/cluster1/esxi1
+
+        HostSystem:host-11 /dc/host/cluster1/esxi2
+
+        HostSystem:host-12 /dc/host/cluster1/esxi3
+
         :param str resource_name: The name of the resource.
         :param VmfsDatastoreArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.

pulumi_vsphere/vnic.py

@@ -433,13 +433,18 @@ class Vnic(pulumi.CustomResource):
             ])
         ```
 
-        ## Importing
+        ## Import
+
+        An existing vNic can be imported into this resource
 
-        An existing vNic can be [imported][docs-import] into this resource
         via supplying the vNic's ID. An example is below:
 
         [docs-import]: /docs/import/index.html
 
+        ```sh
+        $ pulumi import vsphere:index/vnic:Vnic vnic host-123_vmk2
+        ```
+
         The above would import the vnic `vmk2` from host with ID `host-123`.
 
         :param str resource_name: The name of the resource.
@@ -530,13 +535,18 @@ class Vnic(pulumi.CustomResource):
             ])
         ```
 
-        ## Importing
+        ## Import
+
+        An existing vNic can be imported into this resource
 
-        An existing vNic can be [imported][docs-import] into this resource
         via supplying the vNic's ID. An example is below:
 
         [docs-import]: /docs/import/index.html
 
+        ```sh
+        $ pulumi import vsphere:index/vnic:Vnic vnic host-123_vmk2
+        ```
+
         The above would import the vnic `vmk2` from host with ID `host-123`.
 
         :param str resource_name: The name of the resource.

{pulumi_vsphere-4.12.0a1727221820.dist-info → pulumi_vsphere-4.12.0a1727889180.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pulumi_vsphere
-Version: 4.12.0a1727221820
+Version: 4.12.0a1727889180
 Summary: A Pulumi package for creating vsphere resources
 License: Apache-2.0
 Project-URL: Homepage, https://pulumi.io