pulumi-vsphere 4.10.0a1710245029__py3-none-any.whl → 4.13.0a1736836157__py3-none-any.whl

pulumi_vsphere/vmfs_datastore.py

@@ -4,9 +4,14 @@
 
 import copy
 import warnings
+import sys
 import pulumi
 import pulumi.runtime
 from typing import Any, Mapping, Optional, Sequence, Union, overload
+if sys.version_info >= (3, 11):
+    from typing import NotRequired, TypedDict, TypeAlias
+else:
+    from typing_extensions import NotRequired, TypedDict, TypeAlias
 from . import _utilities
 
 __all__ = ['VmfsDatastoreArgs', 'VmfsDatastore']
@@ -461,7 +466,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 +636,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

@@ -4,9 +4,14 @@
 
 import copy
 import warnings
+import sys
 import pulumi
 import pulumi.runtime
 from typing import Any, Mapping, Optional, Sequence, Union, overload
+if sys.version_info >= (3, 11):
+    from typing import NotRequired, TypedDict, TypeAlias
+else:
+    from typing_extensions import NotRequired, TypedDict, TypeAlias
 from . import _utilities
 from . import outputs
 from ._inputs import *
@@ -30,7 +35,7 @@ class VnicArgs:
         The set of arguments for constructing a Vnic resource.
         :param pulumi.Input[str] host: ESX host the interface belongs to
         :param pulumi.Input[str] distributed_port_group: Key of the distributed portgroup the nic will connect to.
-        :param pulumi.Input[str] distributed_switch_port: UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        :param pulumi.Input[str] distributed_switch_port: UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         :param pulumi.Input['VnicIpv4Args'] ipv4: IPv4 settings. Either this or `ipv6` needs to be set. See IPv4 options below.
         :param pulumi.Input['VnicIpv6Args'] ipv6: IPv6 settings. Either this or `ipv6` needs to be set. See IPv6 options below.
         :param pulumi.Input[str] mac: MAC address of the interface.
@@ -87,7 +92,7 @@ class VnicArgs:
     @pulumi.getter(name="distributedSwitchPort")
     def distributed_switch_port(self) -> Optional[pulumi.Input[str]]:
         """
-        UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         """
         return pulumi.get(self, "distributed_switch_port")
 
@@ -196,7 +201,7 @@ class _VnicState:
         """
         Input properties used for looking up and filtering Vnic resources.
         :param pulumi.Input[str] distributed_port_group: Key of the distributed portgroup the nic will connect to.
-        :param pulumi.Input[str] distributed_switch_port: UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        :param pulumi.Input[str] distributed_switch_port: UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         :param pulumi.Input[str] host: ESX host the interface belongs to
         :param pulumi.Input['VnicIpv4Args'] ipv4: IPv4 settings. Either this or `ipv6` needs to be set. See IPv4 options below.
         :param pulumi.Input['VnicIpv6Args'] ipv6: IPv6 settings. Either this or `ipv6` needs to be set. See IPv6 options below.
@@ -243,7 +248,7 @@ class _VnicState:
     @pulumi.getter(name="distributedSwitchPort")
     def distributed_switch_port(self) -> Optional[pulumi.Input[str]]:
         """
-        UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         """
         return pulumi.get(self, "distributed_switch_port")
 
@@ -356,8 +361,8 @@ class Vnic(pulumi.CustomResource):
                  distributed_port_group: Optional[pulumi.Input[str]] = None,
                  distributed_switch_port: Optional[pulumi.Input[str]] = None,
                  host: Optional[pulumi.Input[str]] = None,
-                 ipv4: Optional[pulumi.Input[pulumi.InputType['VnicIpv4Args']]] = None,
-                 ipv6: Optional[pulumi.Input[pulumi.InputType['VnicIpv6Args']]] = None,
+                 ipv4: Optional[pulumi.Input[Union['VnicIpv4Args', 'VnicIpv4ArgsDict']]] = None,
+                 ipv6: Optional[pulumi.Input[Union['VnicIpv6Args', 'VnicIpv6ArgsDict']]] = None,
                  mac: Optional[pulumi.Input[str]] = None,
                  mtu: Optional[pulumi.Input[int]] = None,
                  netstack: Optional[pulumi.Input[str]] = None,
@@ -369,94 +374,91 @@ class Vnic(pulumi.CustomResource):
 
         ## Example Usage
 
-        ### S
-
         ### Create a vnic attached to a distributed virtual switch using the vmotion TCP/IP stack
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_vsphere as vsphere
 
-        dc = vsphere.get_datacenter(name="mydc")
-        h1 = vsphere.get_host(name="esxi1.host.test",
-            datacenter_id=dc.id)
-        d1 = vsphere.DistributedVirtualSwitch("d1",
-            datacenter_id=dc.id,
-            hosts=[vsphere.DistributedVirtualSwitchHostArgs(
-                host_system_id=h1.id,
-                devices=["vnic3"],
-            )])
-        p1 = vsphere.DistributedPortGroup("p1",
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        host = vsphere.get_host(name="esxi-01.example.com",
+            datacenter_id=datacenter.id)
+        vds = vsphere.DistributedVirtualSwitch("vds",
+            name="vds-01",
+            datacenter_id=datacenter.id,
+            hosts=[{
+                "host_system_id": host.id,
+                "devices": ["vnic3"],
+            }])
+        pg = vsphere.DistributedPortGroup("pg",
+            name="pg-01",
             vlan_id=1234,
-            distributed_virtual_switch_uuid=d1.id)
-        v1 = vsphere.Vnic("v1",
-            host=h1.id,
-            distributed_switch_port=d1.id,
-            distributed_port_group=p1.id,
-            ipv4=vsphere.VnicIpv4Args(
-                dhcp=True,
-            ),
+            distributed_virtual_switch_uuid=vds.id)
+        vnic = vsphere.Vnic("vnic",
+            host=host.id,
+            distributed_switch_port=vds.id,
+            distributed_port_group=pg.id,
+            ipv4={
+                "dhcp": True,
+            },
             netstack="vmotion")
         ```
-        <!--End PulumiCodeChooser -->
 
         ### Create a vnic attached to a portgroup using the default TCP/IP stack
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_vsphere as vsphere
 
-        dc = vsphere.get_datacenter(name="mydc")
-        h1 = vsphere.get_host(name="esxi1.host.test",
-            datacenter_id=dc.id)
-        hvs1 = vsphere.HostVirtualSwitch("hvs1",
-            host_system_id=h1.id,
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        host = vsphere.get_host(name="esxi-01.example.com",
+            datacenter_id=datacenter.id)
+        hvs = vsphere.HostVirtualSwitch("hvs",
+            name="hvs-01",
+            host_system_id=host.id,
             network_adapters=[
                 "vmnic3",
                 "vmnic4",
             ],
             active_nics=["vmnic3"],
             standby_nics=["vmnic4"])
-        p1 = vsphere.HostPortGroup("p1",
-            virtual_switch_name=hvs1.name,
-            host_system_id=h1.id)
-        v1 = vsphere.Vnic("v1",
-            host=h1.id,
-            portgroup=p1.name,
-            ipv4=vsphere.VnicIpv4Args(
-                dhcp=True,
-            ),
+        pg = vsphere.HostPortGroup("pg",
+            name="pg-01",
+            virtual_switch_name=hvs.name,
+            host_system_id=host.id)
+        vnic = vsphere.Vnic("vnic",
+            host=host.id,
+            portgroup=pg.name,
+            ipv4={
+                "dhcp": True,
+            },
             services=[
                 "vsan",
                 "management",
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
-        ## 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
 
-        <!--Start PulumiCodeChooser -->
-        ```python
-        import pulumi
+        ```sh
+        $ pulumi import vsphere:index/vnic:Vnic vnic host-123_vmk2
         ```
-        <!--End PulumiCodeChooser -->
 
         The above would import the vnic `vmk2` from host with ID `host-123`.
 
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] distributed_port_group: Key of the distributed portgroup the nic will connect to.
-        :param pulumi.Input[str] distributed_switch_port: UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        :param pulumi.Input[str] distributed_switch_port: UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         :param pulumi.Input[str] host: ESX host the interface belongs to
-        :param pulumi.Input[pulumi.InputType['VnicIpv4Args']] ipv4: IPv4 settings. Either this or `ipv6` needs to be set. See IPv4 options below.
-        :param pulumi.Input[pulumi.InputType['VnicIpv6Args']] ipv6: IPv6 settings. Either this or `ipv6` needs to be set. See IPv6 options below.
+        :param pulumi.Input[Union['VnicIpv4Args', 'VnicIpv4ArgsDict']] ipv4: IPv4 settings. Either this or `ipv6` needs to be set. See IPv4 options below.
+        :param pulumi.Input[Union['VnicIpv6Args', 'VnicIpv6ArgsDict']] ipv6: IPv6 settings. Either this or `ipv6` needs to be set. See IPv6 options below.
         :param pulumi.Input[str] mac: MAC address of the interface.
         :param pulumi.Input[int] mtu: MTU of the interface.
         :param pulumi.Input[str] netstack: TCP/IP stack setting for this interface. Possible values are `defaultTcpipStack``, 'vmotion', 'vSphereProvisioning'. Changing this will force the creation of a new interface since it's not possible to change the stack once it gets created. (Default:`defaultTcpipStack`)
@@ -474,84 +476,81 @@ class Vnic(pulumi.CustomResource):
 
         ## Example Usage
 
-        ### S
-
         ### Create a vnic attached to a distributed virtual switch using the vmotion TCP/IP stack
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_vsphere as vsphere
 
-        dc = vsphere.get_datacenter(name="mydc")
-        h1 = vsphere.get_host(name="esxi1.host.test",
-            datacenter_id=dc.id)
-        d1 = vsphere.DistributedVirtualSwitch("d1",
-            datacenter_id=dc.id,
-            hosts=[vsphere.DistributedVirtualSwitchHostArgs(
-                host_system_id=h1.id,
-                devices=["vnic3"],
-            )])
-        p1 = vsphere.DistributedPortGroup("p1",
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        host = vsphere.get_host(name="esxi-01.example.com",
+            datacenter_id=datacenter.id)
+        vds = vsphere.DistributedVirtualSwitch("vds",
+            name="vds-01",
+            datacenter_id=datacenter.id,
+            hosts=[{
+                "host_system_id": host.id,
+                "devices": ["vnic3"],
+            }])
+        pg = vsphere.DistributedPortGroup("pg",
+            name="pg-01",
             vlan_id=1234,
-            distributed_virtual_switch_uuid=d1.id)
-        v1 = vsphere.Vnic("v1",
-            host=h1.id,
-            distributed_switch_port=d1.id,
-            distributed_port_group=p1.id,
-            ipv4=vsphere.VnicIpv4Args(
-                dhcp=True,
-            ),
+            distributed_virtual_switch_uuid=vds.id)
+        vnic = vsphere.Vnic("vnic",
+            host=host.id,
+            distributed_switch_port=vds.id,
+            distributed_port_group=pg.id,
+            ipv4={
+                "dhcp": True,
+            },
             netstack="vmotion")
         ```
-        <!--End PulumiCodeChooser -->
 
         ### Create a vnic attached to a portgroup using the default TCP/IP stack
 
-        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_vsphere as vsphere
 
-        dc = vsphere.get_datacenter(name="mydc")
-        h1 = vsphere.get_host(name="esxi1.host.test",
-            datacenter_id=dc.id)
-        hvs1 = vsphere.HostVirtualSwitch("hvs1",
-            host_system_id=h1.id,
+        datacenter = vsphere.get_datacenter(name="dc-01")
+        host = vsphere.get_host(name="esxi-01.example.com",
+            datacenter_id=datacenter.id)
+        hvs = vsphere.HostVirtualSwitch("hvs",
+            name="hvs-01",
+            host_system_id=host.id,
             network_adapters=[
                 "vmnic3",
                 "vmnic4",
             ],
             active_nics=["vmnic3"],
             standby_nics=["vmnic4"])
-        p1 = vsphere.HostPortGroup("p1",
-            virtual_switch_name=hvs1.name,
-            host_system_id=h1.id)
-        v1 = vsphere.Vnic("v1",
-            host=h1.id,
-            portgroup=p1.name,
-            ipv4=vsphere.VnicIpv4Args(
-                dhcp=True,
-            ),
+        pg = vsphere.HostPortGroup("pg",
+            name="pg-01",
+            virtual_switch_name=hvs.name,
+            host_system_id=host.id)
+        vnic = vsphere.Vnic("vnic",
+            host=host.id,
+            portgroup=pg.name,
+            ipv4={
+                "dhcp": True,
+            },
             services=[
                 "vsan",
                 "management",
             ])
         ```
-        <!--End PulumiCodeChooser -->
 
-        ## 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
 
-        <!--Start PulumiCodeChooser -->
-        ```python
-        import pulumi
+        ```sh
+        $ pulumi import vsphere:index/vnic:Vnic vnic host-123_vmk2
         ```
-        <!--End PulumiCodeChooser -->
 
         The above would import the vnic `vmk2` from host with ID `host-123`.
 
@@ -573,8 +572,8 @@ class Vnic(pulumi.CustomResource):
                  distributed_port_group: Optional[pulumi.Input[str]] = None,
                  distributed_switch_port: Optional[pulumi.Input[str]] = None,
                  host: Optional[pulumi.Input[str]] = None,
-                 ipv4: Optional[pulumi.Input[pulumi.InputType['VnicIpv4Args']]] = None,
-                 ipv6: Optional[pulumi.Input[pulumi.InputType['VnicIpv6Args']]] = None,
+                 ipv4: Optional[pulumi.Input[Union['VnicIpv4Args', 'VnicIpv4ArgsDict']]] = None,
+                 ipv6: Optional[pulumi.Input[Union['VnicIpv6Args', 'VnicIpv6ArgsDict']]] = None,
                  mac: Optional[pulumi.Input[str]] = None,
                  mtu: Optional[pulumi.Input[int]] = None,
                  netstack: Optional[pulumi.Input[str]] = None,
@@ -614,8 +613,8 @@ class Vnic(pulumi.CustomResource):
             distributed_port_group: Optional[pulumi.Input[str]] = None,
             distributed_switch_port: Optional[pulumi.Input[str]] = None,
             host: Optional[pulumi.Input[str]] = None,
-            ipv4: Optional[pulumi.Input[pulumi.InputType['VnicIpv4Args']]] = None,
-            ipv6: Optional[pulumi.Input[pulumi.InputType['VnicIpv6Args']]] = None,
+            ipv4: Optional[pulumi.Input[Union['VnicIpv4Args', 'VnicIpv4ArgsDict']]] = None,
+            ipv6: Optional[pulumi.Input[Union['VnicIpv6Args', 'VnicIpv6ArgsDict']]] = None,
             mac: Optional[pulumi.Input[str]] = None,
             mtu: Optional[pulumi.Input[int]] = None,
             netstack: Optional[pulumi.Input[str]] = None,
@@ -629,10 +628,10 @@ class Vnic(pulumi.CustomResource):
         :param pulumi.Input[str] id: The unique provider ID of the resource to lookup.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] distributed_port_group: Key of the distributed portgroup the nic will connect to.
-        :param pulumi.Input[str] distributed_switch_port: UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        :param pulumi.Input[str] distributed_switch_port: UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         :param pulumi.Input[str] host: ESX host the interface belongs to
-        :param pulumi.Input[pulumi.InputType['VnicIpv4Args']] ipv4: IPv4 settings. Either this or `ipv6` needs to be set. See IPv4 options below.
-        :param pulumi.Input[pulumi.InputType['VnicIpv6Args']] ipv6: IPv6 settings. Either this or `ipv6` needs to be set. See IPv6 options below.
+        :param pulumi.Input[Union['VnicIpv4Args', 'VnicIpv4ArgsDict']] ipv4: IPv4 settings. Either this or `ipv6` needs to be set. See IPv4 options below.
+        :param pulumi.Input[Union['VnicIpv6Args', 'VnicIpv6ArgsDict']] ipv6: IPv6 settings. Either this or `ipv6` needs to be set. See IPv6 options below.
         :param pulumi.Input[str] mac: MAC address of the interface.
         :param pulumi.Input[int] mtu: MTU of the interface.
         :param pulumi.Input[str] netstack: TCP/IP stack setting for this interface. Possible values are `defaultTcpipStack``, 'vmotion', 'vSphereProvisioning'. Changing this will force the creation of a new interface since it's not possible to change the stack once it gets created. (Default:`defaultTcpipStack`)
@@ -667,7 +666,7 @@ class Vnic(pulumi.CustomResource):
     @pulumi.getter(name="distributedSwitchPort")
     def distributed_switch_port(self) -> pulumi.Output[Optional[str]]:
         """
-        UUID of the DVSwitch the nic will be attached to. Do not set if you set portgroup.
+        UUID of the vdswitch the nic will be attached to. Do not set if you set portgroup.
         """
         return pulumi.get(self, "distributed_switch_port")