pulumi-vsphere 4.12.0__py3-none-any.whl → 4.12.0a1725603256__py3-none-any.whl

pulumi_vsphere/distributed_port_group.py

@@ -4,14 +4,9 @@
 
 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 *
@@ -1704,146 +1699,7 @@ class DistributedPortGroup(pulumi.CustomResource):
                  vlan_ranges: Optional[pulumi.Input[Sequence[pulumi.Input[Union['DistributedPortGroupVlanRangeArgs', 'DistributedPortGroupVlanRangeArgsDict']]]]] = None,
                  __props__=None):
         """
-        The `DistributedPortGroup` resource can be used to manage
-        distributed port groups connected to vSphere Distributed Switches (VDS).
-        A vSphere Distributed Switch can be managed by the
-        `DistributedVirtualSwitch` resource.
-
-        Distributed port groups can be used as networks for virtual machines, allowing
-        the virtual machines to use the networking supplied by a vSphere Distributed
-        Switch, with a set of policies that apply to that individual network, if
-        desired.
-
-        * For an overview on vSphere networking concepts, refer to the vSphere
-        [product documentation][ref-vsphere-net-concepts].
-
-        * For more information on distributed port groups, refer to the vSphere
-        [product documentation][ref-vsphere-dvportgroup].
-
-        [ref-vsphere-net-concepts]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-2B11DBB8-CB3C-4AFF-8885-EFEA0FC562F4.html
-        [ref-vsphere-dvportgroup]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-69933F6E-2442-46CF-AA17-1196CB9A0A09.html
-
-        > **NOTE:** This resource requires vCenter and is not available on
-        direct ESXi host connections.
-
-        ## Example Usage
-
-        The configuration below builds on the example given in the
-        `DistributedVirtualSwitch` resource by
-        adding the `DistributedPortGroup` resource, attaching itself to the
-        vSphere Distributed Switch and assigning VLAN ID 1000.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        config = pulumi.Config()
-        hosts = config.get_object("hosts")
-        if hosts is None:
-            hosts = [
-                "esxi-01.example.com",
-                "esxi-02.example.com",
-                "esxi-03.example.com",
-            ]
-        network_interfaces = config.get_object("networkInterfaces")
-        if network_interfaces is None:
-            network_interfaces = [
-                "vmnic0",
-                "vmnic1",
-                "vmnic2",
-                "vmnic3",
-            ]
-        datacenter = vsphere.get_datacenter(name="dc-01")
-        host = [vsphere.get_host(name=hosts[__index],
-            datacenter_id=datacenter.id) for __index in range(len(hosts))]
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter.id,
-            uplinks=[
-                "uplink1",
-                "uplink2",
-                "uplink3",
-                "uplink4",
-            ],
-            active_uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            standby_uplinks=[
-                "uplink3",
-                "uplink4",
-            ],
-            hosts=[
-                {
-                    "host_system_id": host[0].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[1].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[2].id,
-                    "devices": [network_interfaces],
-                },
-            ])
-        pg = vsphere.DistributedPortGroup("pg",
-            name="pg-01",
-            distributed_virtual_switch_uuid=vds.id,
-            vlan_id=1000)
-        ```
-
-        ### Overriding VDS policies
-
-        All of the default port policies available in the
-        `DistributedVirtualSwitch` resource can be overridden on the port
-        group level by specifying new settings for them.
-
-        As an example, we also take this example from the
-        `DistributedVirtualSwitch` resource where we manually specify our
-        uplink count and uplink order. While the vSphere Distributed Switch has a
-        default policy of using the first uplink as an active uplink and the second
-        one as a standby, the overridden port group policy means that both uplinks
-        will be used as active uplinks in this specific port group.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter["id"],
-            uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            active_uplinks=["uplink1"],
-            standby_uplinks=["uplink2"])
-        pg = vsphere.DistributedPortGroup("pg",
-            name="pg-01",
-            distributed_virtual_switch_uuid=vds.id,
-            vlan_id=1000,
-            active_uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            standby_uplinks=[])
-        ```
-
-        ## Import
-
-        An existing port group can be imported into this resource using
-
-        the managed object id of the port group, via the following command:
-
-        ```sh
-        $ pulumi import vsphere:index/distributedPortGroup:DistributedPortGroup pg /dc-01/network/pg-01
-        ```
-
-        The above would import the port group named `pg-01` that is located in the `dc-01`
-
-        datacenter.
-
+        Create a DistributedPortGroup resource with the given unique name, props, and options.
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[Sequence[pulumi.Input[str]]] active_uplinks: List of active uplinks used for load balancing, matching the names of the uplinks assigned in the DVS.
@@ -1928,146 +1784,7 @@ class DistributedPortGroup(pulumi.CustomResource):
                  args: DistributedPortGroupArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        The `DistributedPortGroup` resource can be used to manage
-        distributed port groups connected to vSphere Distributed Switches (VDS).
-        A vSphere Distributed Switch can be managed by the
-        `DistributedVirtualSwitch` resource.
-
-        Distributed port groups can be used as networks for virtual machines, allowing
-        the virtual machines to use the networking supplied by a vSphere Distributed
-        Switch, with a set of policies that apply to that individual network, if
-        desired.
-
-        * For an overview on vSphere networking concepts, refer to the vSphere
-        [product documentation][ref-vsphere-net-concepts].
-
-        * For more information on distributed port groups, refer to the vSphere
-        [product documentation][ref-vsphere-dvportgroup].
-
-        [ref-vsphere-net-concepts]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-2B11DBB8-CB3C-4AFF-8885-EFEA0FC562F4.html
-        [ref-vsphere-dvportgroup]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-69933F6E-2442-46CF-AA17-1196CB9A0A09.html
-
-        > **NOTE:** This resource requires vCenter and is not available on
-        direct ESXi host connections.
-
-        ## Example Usage
-
-        The configuration below builds on the example given in the
-        `DistributedVirtualSwitch` resource by
-        adding the `DistributedPortGroup` resource, attaching itself to the
-        vSphere Distributed Switch and assigning VLAN ID 1000.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        config = pulumi.Config()
-        hosts = config.get_object("hosts")
-        if hosts is None:
-            hosts = [
-                "esxi-01.example.com",
-                "esxi-02.example.com",
-                "esxi-03.example.com",
-            ]
-        network_interfaces = config.get_object("networkInterfaces")
-        if network_interfaces is None:
-            network_interfaces = [
-                "vmnic0",
-                "vmnic1",
-                "vmnic2",
-                "vmnic3",
-            ]
-        datacenter = vsphere.get_datacenter(name="dc-01")
-        host = [vsphere.get_host(name=hosts[__index],
-            datacenter_id=datacenter.id) for __index in range(len(hosts))]
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter.id,
-            uplinks=[
-                "uplink1",
-                "uplink2",
-                "uplink3",
-                "uplink4",
-            ],
-            active_uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            standby_uplinks=[
-                "uplink3",
-                "uplink4",
-            ],
-            hosts=[
-                {
-                    "host_system_id": host[0].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[1].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[2].id,
-                    "devices": [network_interfaces],
-                },
-            ])
-        pg = vsphere.DistributedPortGroup("pg",
-            name="pg-01",
-            distributed_virtual_switch_uuid=vds.id,
-            vlan_id=1000)
-        ```
-
-        ### Overriding VDS policies
-
-        All of the default port policies available in the
-        `DistributedVirtualSwitch` resource can be overridden on the port
-        group level by specifying new settings for them.
-
-        As an example, we also take this example from the
-        `DistributedVirtualSwitch` resource where we manually specify our
-        uplink count and uplink order. While the vSphere Distributed Switch has a
-        default policy of using the first uplink as an active uplink and the second
-        one as a standby, the overridden port group policy means that both uplinks
-        will be used as active uplinks in this specific port group.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter["id"],
-            uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            active_uplinks=["uplink1"],
-            standby_uplinks=["uplink2"])
-        pg = vsphere.DistributedPortGroup("pg",
-            name="pg-01",
-            distributed_virtual_switch_uuid=vds.id,
-            vlan_id=1000,
-            active_uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            standby_uplinks=[])
-        ```
-
-        ## Import
-
-        An existing port group can be imported into this resource using
-
-        the managed object id of the port group, via the following command:
-
-        ```sh
-        $ pulumi import vsphere:index/distributedPortGroup:DistributedPortGroup pg /dc-01/network/pg-01
-        ```
-
-        The above would import the port group named `pg-01` that is located in the `dc-01`
-
-        datacenter.
-
+        Create a DistributedPortGroup resource with the given unique name, props, and options.
         :param str resource_name: The name of the resource.
         :param DistributedPortGroupArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.

pulumi_vsphere/distributed_virtual_switch.py

@@ -4,14 +4,9 @@
 
 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 *
@@ -3244,134 +3239,7 @@ class DistributedVirtualSwitch(pulumi.CustomResource):
                  vsan_share_level: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        The `DistributedVirtualSwitch` resource can be used to manage vSphere
-        Distributed Switches (VDS).
-
-        An essential component of a distributed, scalable vSphere infrastructure, the
-        VDS provides centralized management and monitoring of the networking
-        configuration for all the hosts that are associated with the switch.
-        In addition to adding distributed port groups
-        (see the `DistributedPortGroup` resource)
-        that can be used as networks for virtual machines, a VDS can be configured to
-        perform advanced high availability, traffic shaping, network monitoring, etc.
-
-        For an overview on vSphere networking concepts, see
-        [this page][ref-vsphere-net-concepts].
-
-        For more information on the VDS, see [this page][ref-vsphere-vds].
-
-        [ref-vsphere-net-concepts]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-2B11DBB8-CB3C-4AFF-8885-EFEA0FC562F4.html
-        [ref-vsphere-vds]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-375B45C7-684C-4C51-BA3C-70E48DFABF04.html
-
-        > **NOTE:** This resource requires vCenter and is not available on
-        direct ESXi host connections.
-
-        ## Example Usage
-
-        The following example below demonstrates a "standard" example of configuring a
-        VDS in a 3-node vSphere datacenter named `dc1`, across 4 NICs with two being
-        used as active, and two being used as passive. Note that the NIC failover order
-        propagates to any port groups configured on this VDS and can be overridden.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        config = pulumi.Config()
-        hosts = config.get_object("hosts")
-        if hosts is None:
-            hosts = [
-                "esxi-01.example.com",
-                "esxi-02.example.com",
-                "esxi-03.example.com",
-            ]
-        network_interfaces = config.get_object("networkInterfaces")
-        if network_interfaces is None:
-            network_interfaces = [
-                "vmnic0",
-                "vmnic1",
-                "vmnic2",
-                "vmnic3",
-            ]
-        datacenter = vsphere.get_datacenter(name="dc-01")
-        host = [vsphere.get_host(name=hosts[__index],
-            datacenter_id=datacenter.id) for __index in range(len(hosts))]
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter.id,
-            uplinks=[
-                "uplink1",
-                "uplink2",
-                "uplink3",
-                "uplink4",
-            ],
-            active_uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            standby_uplinks=[
-                "uplink3",
-                "uplink4",
-            ],
-            hosts=[
-                {
-                    "host_system_id": host[0].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[1].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[2].id,
-                    "devices": [network_interfaces],
-                },
-            ])
-        ```
-
-        ### Uplink name and count control
-
-        The following abridged example below demonstrates how you can manage the number
-        of uplinks, and the name of the uplinks via the `uplinks` parameter.
-
-        Note that if you change the uplink naming and count after creating the VDS, you
-        may need to explicitly specify `active_uplinks` and `standby_uplinks` as these
-        values are saved to state after creation, regardless of being
-        specified in config, and will drift if not modified, causing errors.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter["id"],
-            uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            active_uplinks=["uplink1"],
-            standby_uplinks=["uplink2"])
-        ```
-
-        > **NOTE:** The default uplink names when a VDS is created are `uplink1`
-        through to `uplink4`, however this default is not guaranteed to be stable and
-        you are encouraged to set your own.
-
-        ## Import
-
-        An existing VDS can be imported into this resource via the path
-
-        to the VDS, via the following command:
-
-        ```sh
-        $ pulumi import vsphere:index/distributedVirtualSwitch:DistributedVirtualSwitch vds /dc-01/network/vds-01
-        ```
-
-        The above would import the VDS named `vds-01` that is located in the `dc-01`
-
-        datacenter.
-
+        Create a DistributedVirtualSwitch resource with the given unique name, props, and options.
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[Sequence[pulumi.Input[str]]] active_uplinks: List of active uplinks used for load balancing, matching the names of the uplinks assigned in the DVS.
@@ -3497,134 +3365,7 @@ class DistributedVirtualSwitch(pulumi.CustomResource):
                  args: DistributedVirtualSwitchArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        The `DistributedVirtualSwitch` resource can be used to manage vSphere
-        Distributed Switches (VDS).
-
-        An essential component of a distributed, scalable vSphere infrastructure, the
-        VDS provides centralized management and monitoring of the networking
-        configuration for all the hosts that are associated with the switch.
-        In addition to adding distributed port groups
-        (see the `DistributedPortGroup` resource)
-        that can be used as networks for virtual machines, a VDS can be configured to
-        perform advanced high availability, traffic shaping, network monitoring, etc.
-
-        For an overview on vSphere networking concepts, see
-        [this page][ref-vsphere-net-concepts].
-
-        For more information on the VDS, see [this page][ref-vsphere-vds].
-
-        [ref-vsphere-net-concepts]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-2B11DBB8-CB3C-4AFF-8885-EFEA0FC562F4.html
-        [ref-vsphere-vds]: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-375B45C7-684C-4C51-BA3C-70E48DFABF04.html
-
-        > **NOTE:** This resource requires vCenter and is not available on
-        direct ESXi host connections.
-
-        ## Example Usage
-
-        The following example below demonstrates a "standard" example of configuring a
-        VDS in a 3-node vSphere datacenter named `dc1`, across 4 NICs with two being
-        used as active, and two being used as passive. Note that the NIC failover order
-        propagates to any port groups configured on this VDS and can be overridden.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        config = pulumi.Config()
-        hosts = config.get_object("hosts")
-        if hosts is None:
-            hosts = [
-                "esxi-01.example.com",
-                "esxi-02.example.com",
-                "esxi-03.example.com",
-            ]
-        network_interfaces = config.get_object("networkInterfaces")
-        if network_interfaces is None:
-            network_interfaces = [
-                "vmnic0",
-                "vmnic1",
-                "vmnic2",
-                "vmnic3",
-            ]
-        datacenter = vsphere.get_datacenter(name="dc-01")
-        host = [vsphere.get_host(name=hosts[__index],
-            datacenter_id=datacenter.id) for __index in range(len(hosts))]
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter.id,
-            uplinks=[
-                "uplink1",
-                "uplink2",
-                "uplink3",
-                "uplink4",
-            ],
-            active_uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            standby_uplinks=[
-                "uplink3",
-                "uplink4",
-            ],
-            hosts=[
-                {
-                    "host_system_id": host[0].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[1].id,
-                    "devices": [network_interfaces],
-                },
-                {
-                    "host_system_id": host[2].id,
-                    "devices": [network_interfaces],
-                },
-            ])
-        ```
-
-        ### Uplink name and count control
-
-        The following abridged example below demonstrates how you can manage the number
-        of uplinks, and the name of the uplinks via the `uplinks` parameter.
-
-        Note that if you change the uplink naming and count after creating the VDS, you
-        may need to explicitly specify `active_uplinks` and `standby_uplinks` as these
-        values are saved to state after creation, regardless of being
-        specified in config, and will drift if not modified, causing errors.
-
-        ```python
-        import pulumi
-        import pulumi_vsphere as vsphere
-
-        vds = vsphere.DistributedVirtualSwitch("vds",
-            name="vds-01",
-            datacenter_id=datacenter["id"],
-            uplinks=[
-                "uplink1",
-                "uplink2",
-            ],
-            active_uplinks=["uplink1"],
-            standby_uplinks=["uplink2"])
-        ```
-
-        > **NOTE:** The default uplink names when a VDS is created are `uplink1`
-        through to `uplink4`, however this default is not guaranteed to be stable and
-        you are encouraged to set your own.
-
-        ## Import
-
-        An existing VDS can be imported into this resource via the path
-
-        to the VDS, via the following command:
-
-        ```sh
-        $ pulumi import vsphere:index/distributedVirtualSwitch:DistributedVirtualSwitch vds /dc-01/network/vds-01
-        ```
-
-        The above would import the VDS named `vds-01` that is located in the `dc-01`
-
-        datacenter.
-
+        Create a DistributedVirtualSwitch resource with the given unique name, props, and options.
         :param str resource_name: The name of the resource.
         :param DistributedVirtualSwitchArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.

pulumi_vsphere/dpm_host_override.py

@@ -4,14 +4,9 @@
 
 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__ = ['DpmHostOverrideArgs', 'DpmHostOverride']
@@ -205,35 +200,7 @@ class DpmHostOverride(pulumi.CustomResource):
                  host_system_id: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        The `DpmHostOverride` resource can be used to add a DPM override to a
-        cluster for a particular host. This allows you to control the power management
-        settings for individual hosts in the cluster while leaving any unspecified ones
-        at the default power management settings.
-
-        For more information on DPM within vSphere clusters, see [this
-        page][ref-vsphere-cluster-dpm].
-
-        [ref-vsphere-cluster-dpm]: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-resource-management/GUID-5E5E349A-4644-4C9C-B434-1C0243EBDC80.html
-
-        > **NOTE:** This resource requires vCenter and is not available on direct ESXi
-        connections.
-
-        ## Import
-
-        An existing override can be imported into this resource by
-
-        supplying both the path to the cluster, and the path to the host, to `terraform
-
-        import`. If no override exists, an error will be given.  An example is below:
-
-        ```sh
-        $ pulumi import vsphere:index/dpmHostOverride:DpmHostOverride dpm_host_override \\
-        ```
-
-          '{"compute_cluster_path": "/dc1/host/cluster1", \\
-
-          "host_path": "/dc1/host/esxi1"}'
-
+        Create a DpmHostOverride resource with the given unique name, props, and options.
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
         :param pulumi.Input[str] compute_cluster_id: The managed object reference
@@ -257,35 +224,7 @@ class DpmHostOverride(pulumi.CustomResource):
                  args: DpmHostOverrideArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        The `DpmHostOverride` resource can be used to add a DPM override to a
-        cluster for a particular host. This allows you to control the power management
-        settings for individual hosts in the cluster while leaving any unspecified ones
-        at the default power management settings.
-
-        For more information on DPM within vSphere clusters, see [this
-        page][ref-vsphere-cluster-dpm].
-
-        [ref-vsphere-cluster-dpm]: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-resource-management/GUID-5E5E349A-4644-4C9C-B434-1C0243EBDC80.html
-
-        > **NOTE:** This resource requires vCenter and is not available on direct ESXi
-        connections.
-
-        ## Import
-
-        An existing override can be imported into this resource by
-
-        supplying both the path to the cluster, and the path to the host, to `terraform
-
-        import`. If no override exists, an error will be given.  An example is below:
-
-        ```sh
-        $ pulumi import vsphere:index/dpmHostOverride:DpmHostOverride dpm_host_override \\
-        ```
-
-          '{"compute_cluster_path": "/dc1/host/cluster1", \\
-
-          "host_path": "/dc1/host/esxi1"}'
-
+        Create a DpmHostOverride resource with the given unique name, props, and options.
         :param str resource_name: The name of the resource.
         :param DpmHostOverrideArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.