PyPI - pulumi-vsphere - Versions diffs - 4.12.0__py3-none-any.whl → 4.12.0a1725645004__py3-none-any.whl - Mend

pulumi-vsphere 4.12.0py3-none-any.whl → 4.12.0a1725645004py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.

This version of pulumi-vsphere might be problematic. Click here for more details.

Files changed (84) hide show

pulumi_vsphere/_inputs.py +6 -1135
pulumi_vsphere/_utilities.py +1 -1
pulumi_vsphere/compute_cluster.py +2 -181
pulumi_vsphere/compute_cluster_host_group.py +2 -67
pulumi_vsphere/compute_cluster_vm_affinity_rule.py +2 -29
pulumi_vsphere/compute_cluster_vm_anti_affinity_rule.py +2 -41
pulumi_vsphere/compute_cluster_vm_dependency_rule.py +2 -205
pulumi_vsphere/compute_cluster_vm_group.py +2 -198
pulumi_vsphere/compute_cluster_vm_host_rule.py +2 -73
pulumi_vsphere/config/__init__.pyi +0 -5
pulumi_vsphere/config/vars.py +0 -5
pulumi_vsphere/content_library.py +2 -103
pulumi_vsphere/content_library_item.py +2 -143
pulumi_vsphere/custom_attribute.py +2 -77
pulumi_vsphere/datacenter.py +4 -19
pulumi_vsphere/datastore_cluster.py +2 -63
pulumi_vsphere/datastore_cluster_vm_anti_affinity_rule.py +2 -159
pulumi_vsphere/distributed_port_group.py +2 -285
pulumi_vsphere/distributed_virtual_switch.py +2 -261
pulumi_vsphere/dpm_host_override.py +2 -63
pulumi_vsphere/drs_vm_override.py +2 -67
pulumi_vsphere/entity_permissions.py +0 -5
pulumi_vsphere/file.py +0 -5
pulumi_vsphere/folder.py +2 -141
pulumi_vsphere/get_compute_cluster.py +4 -15
pulumi_vsphere/get_compute_cluster_host_group.py +6 -17
pulumi_vsphere/get_content_library.py +4 -12
pulumi_vsphere/get_content_library_item.py +4 -16
pulumi_vsphere/get_custom_attribute.py +4 -13
pulumi_vsphere/get_datacenter.py +7 -29
pulumi_vsphere/get_datastore.py +4 -16
pulumi_vsphere/get_datastore_cluster.py +5 -30
pulumi_vsphere/get_datastore_stats.py +4 -16
pulumi_vsphere/get_distributed_virtual_switch.py +4 -15
pulumi_vsphere/get_dynamic.py +4 -16
pulumi_vsphere/get_folder.py +4 -12
pulumi_vsphere/get_guest_os_customization.py +4 -17
pulumi_vsphere/get_host.py +4 -15
pulumi_vsphere/get_host_base_images.py +4 -11
pulumi_vsphere/get_host_pci_device.py +4 -19
pulumi_vsphere/get_host_thumbprint.py +14 -34
pulumi_vsphere/get_host_vgpu_profile.py +4 -15
pulumi_vsphere/get_license.py +4 -17
pulumi_vsphere/get_network.py +5 -65
pulumi_vsphere/get_ovf_vm_template.py +4 -55
pulumi_vsphere/get_policy.py +4 -12
pulumi_vsphere/get_resource_pool.py +4 -14
pulumi_vsphere/get_role.py +4 -18
pulumi_vsphere/get_tag.py +4 -15
pulumi_vsphere/get_tag_category.py +4 -15
pulumi_vsphere/get_vapp_container.py +4 -14
pulumi_vsphere/get_virtual_machine.py +5 -145
pulumi_vsphere/get_vmfs_disks.py +4 -17
pulumi_vsphere/guest_os_customization.py +0 -5
pulumi_vsphere/ha_vm_override.py +2 -163
pulumi_vsphere/host.py +12 -203
pulumi_vsphere/host_port_group.py +2 -17
pulumi_vsphere/host_virtual_switch.py +2 -69
pulumi_vsphere/license.py +0 -5
pulumi_vsphere/nas_datastore.py +2 -67
pulumi_vsphere/offline_software_depot.py +0 -5
pulumi_vsphere/outputs.py +0 -45
pulumi_vsphere/provider.py +0 -5
pulumi_vsphere/pulumi-plugin.json +1 -1
pulumi_vsphere/resource_pool.py +437 -168
pulumi_vsphere/role.py +2 -33
pulumi_vsphere/storage_drs_vm_override.py +2 -133
pulumi_vsphere/supervisor.py +0 -5
pulumi_vsphere/tag.py +2 -159
pulumi_vsphere/tag_category.py +2 -83
pulumi_vsphere/vapp_container.py +2 -163
pulumi_vsphere/vapp_entity.py +2 -147
pulumi_vsphere/virtual_disk.py +2 -81
pulumi_vsphere/virtual_machine.py +2 -100
pulumi_vsphere/virtual_machine_class.py +0 -5
pulumi_vsphere/virtual_machine_snapshot.py +0 -5
pulumi_vsphere/vm_storage_policy.py +0 -5
pulumi_vsphere/vmfs_datastore.py +2 -271
pulumi_vsphere/vnic.py +4 -19
{pulumi_vsphere-4.12.0.dist-info → pulumi_vsphere-4.12.0a1725645004.dist-info}/METADATA +2 -3
pulumi_vsphere-4.12.0a1725645004.dist-info/RECORD +86 -0
{pulumi_vsphere-4.12.0.dist-info → pulumi_vsphere-4.12.0a1725645004.dist-info}/WHEEL +1 -1
pulumi_vsphere-4.12.0.dist-info/RECORD +0 -86
{pulumi_vsphere-4.12.0.dist-info → pulumi_vsphere-4.12.0a1725645004.dist-info}/top_level.txt +0 -0

pulumi_vsphere/virtual_machine.py CHANGED Viewed

@@ -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 *
@@ -92,7 +87,6 @@ class VirtualMachineArgs:
                  tools_upgrade_policy: Optional[pulumi.Input[str]] = None,
                  vapp: Optional[pulumi.Input['VirtualMachineVappArgs']] = None,
                  vbs_enabled: Optional[pulumi.Input[bool]] = None,
-                 vtpm: Optional[pulumi.Input['VirtualMachineVtpmArgs']] = None,
                  vvtd_enabled: Optional[pulumi.Input[bool]] = None,
                  wait_for_guest_ip_timeout: Optional[pulumi.Input[int]] = None,
                  wait_for_guest_net_routable: Optional[pulumi.Input[bool]] = None,
@@ -178,7 +172,6 @@ class VirtualMachineArgs:
         :param pulumi.Input[str] tools_upgrade_policy: Set the upgrade policy for VMware Tools. Can be one of `manual` or `upgradeAtPowerCycle`.
         :param pulumi.Input['VirtualMachineVappArgs'] vapp: vApp configuration data for this virtual machine. Can be used to provide configuration data for OVF images.
         :param pulumi.Input[bool] vbs_enabled: Flag to specify if Virtualization-based security is enabled for this virtual machine.
-        :param pulumi.Input['VirtualMachineVtpmArgs'] vtpm: A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
         :param pulumi.Input[bool] vvtd_enabled: Flag to specify if I/O MMU virtualization, also called Intel Virtualization Technology for Directed I/O (VT-d) and AMD
                I/O Virtualization (AMD-Vi or IOMMU), is enabled.
         :param pulumi.Input[int] wait_for_guest_ip_timeout: The amount of time, in minutes, to wait for an available IP address on this virtual machine. A value less than 1
@@ -329,8 +322,6 @@ class VirtualMachineArgs:
             pulumi.set(__self__, "vapp", vapp)
         if vbs_enabled is not None:
             pulumi.set(__self__, "vbs_enabled", vbs_enabled)
-        if vtpm is not None:
-            pulumi.set(__self__, "vtpm", vtpm)
         if vvtd_enabled is not None:
             pulumi.set(__self__, "vvtd_enabled", vvtd_enabled)
         if wait_for_guest_ip_timeout is not None:
@@ -1194,18 +1185,6 @@ class VirtualMachineArgs:
     def vbs_enabled(self, value: Optional[pulumi.Input[bool]]):
         pulumi.set(self, "vbs_enabled", value)
-    @property
-    @pulumi.getter
-    def vtpm(self) -> Optional[pulumi.Input['VirtualMachineVtpmArgs']]:
-        """
-        A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
-        """
-        return pulumi.get(self, "vtpm")
-    @vtpm.setter
-    def vtpm(self, value: Optional[pulumi.Input['VirtualMachineVtpmArgs']]):
-        pulumi.set(self, "vtpm", value)
     @property
     @pulumi.getter(name="vvtdEnabled")
     def vvtd_enabled(self) -> Optional[pulumi.Input[bool]]:
@@ -1344,7 +1323,6 @@ class _VirtualMachineState:
                  vbs_enabled: Optional[pulumi.Input[bool]] = None,
                  vmware_tools_status: Optional[pulumi.Input[str]] = None,
                  vmx_path: Optional[pulumi.Input[str]] = None,
-                 vtpm: Optional[pulumi.Input['VirtualMachineVtpmArgs']] = None,
                  vvtd_enabled: Optional[pulumi.Input[bool]] = None,
                  wait_for_guest_ip_timeout: Optional[pulumi.Input[int]] = None,
                  wait_for_guest_net_routable: Optional[pulumi.Input[bool]] = None,
@@ -1440,7 +1418,6 @@ class _VirtualMachineState:
         :param pulumi.Input[bool] vbs_enabled: Flag to specify if Virtualization-based security is enabled for this virtual machine.
         :param pulumi.Input[str] vmware_tools_status: The state of  VMware Tools in the guest. This will determine the proper course of action for some device operations.
         :param pulumi.Input[str] vmx_path: The path of the virtual machine configuration file on the datastore in which the virtual machine is placed.
-        :param pulumi.Input['VirtualMachineVtpmArgs'] vtpm: A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
         :param pulumi.Input[bool] vvtd_enabled: Flag to specify if I/O MMU virtualization, also called Intel Virtualization Technology for Directed I/O (VT-d) and AMD
                I/O Virtualization (AMD-Vi or IOMMU), is enabled.
         :param pulumi.Input[int] wait_for_guest_ip_timeout: The amount of time, in minutes, to wait for an available IP address on this virtual machine. A value less than 1
@@ -1614,8 +1591,6 @@ class _VirtualMachineState:
             pulumi.set(__self__, "vmware_tools_status", vmware_tools_status)
         if vmx_path is not None:
             pulumi.set(__self__, "vmx_path", vmx_path)
-        if vtpm is not None:
-            pulumi.set(__self__, "vtpm", vtpm)
         if vvtd_enabled is not None:
             pulumi.set(__self__, "vvtd_enabled", vvtd_enabled)
         if wait_for_guest_ip_timeout is not None:
@@ -2608,18 +2583,6 @@ class _VirtualMachineState:
     def vmx_path(self, value: Optional[pulumi.Input[str]]):
         pulumi.set(self, "vmx_path", value)
-    @property
-    @pulumi.getter
-    def vtpm(self) -> Optional[pulumi.Input['VirtualMachineVtpmArgs']]:
-        """
-        A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
-        """
-        return pulumi.get(self, "vtpm")
-    @vtpm.setter
-    def vtpm(self, value: Optional[pulumi.Input['VirtualMachineVtpmArgs']]):
-        pulumi.set(self, "vtpm", value)
     @property
     @pulumi.getter(name="vvtdEnabled")
     def vvtd_enabled(self) -> Optional[pulumi.Input[bool]]:
@@ -2749,37 +2712,13 @@ class VirtualMachine(pulumi.CustomResource):
                  tools_upgrade_policy: Optional[pulumi.Input[str]] = None,
                  vapp: Optional[pulumi.Input[Union['VirtualMachineVappArgs', 'VirtualMachineVappArgsDict']]] = None,
                  vbs_enabled: Optional[pulumi.Input[bool]] = None,
-                 vtpm: Optional[pulumi.Input[Union['VirtualMachineVtpmArgs', 'VirtualMachineVtpmArgsDict']]] = None,
                  vvtd_enabled: Optional[pulumi.Input[bool]] = None,
                  wait_for_guest_ip_timeout: Optional[pulumi.Input[int]] = None,
                  wait_for_guest_net_routable: Optional[pulumi.Input[bool]] = None,
                  wait_for_guest_net_timeout: Optional[pulumi.Input[int]] = None,
                  __props__=None):
         """
-        ## 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 `Hard Disk`, 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 `Hard Disk 0`, a disk on the same controller with a unit number of `1` would be `Hard Disk 1`, but the next disk, which is on SCSI controller `1` with a unit number of `0`, still becomes `Hard Disk 2`.
-        * 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.
+        Create a VirtualMachine 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] alternate_guest_name: The guest name for the operating system when guest_id is otherGuest or otherGuest64.
@@ -2861,7 +2800,6 @@ class VirtualMachine(pulumi.CustomResource):
         :param pulumi.Input[str] tools_upgrade_policy: Set the upgrade policy for VMware Tools. Can be one of `manual` or `upgradeAtPowerCycle`.
         :param pulumi.Input[Union['VirtualMachineVappArgs', 'VirtualMachineVappArgsDict']] vapp: vApp configuration data for this virtual machine. Can be used to provide configuration data for OVF images.
         :param pulumi.Input[bool] vbs_enabled: Flag to specify if Virtualization-based security is enabled for this virtual machine.
-        :param pulumi.Input[Union['VirtualMachineVtpmArgs', 'VirtualMachineVtpmArgsDict']] vtpm: A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
         :param pulumi.Input[bool] vvtd_enabled: Flag to specify if I/O MMU virtualization, also called Intel Virtualization Technology for Directed I/O (VT-d) and AMD
                I/O Virtualization (AMD-Vi or IOMMU), is enabled.
         :param pulumi.Input[int] wait_for_guest_ip_timeout: The amount of time, in minutes, to wait for an available IP address on this virtual machine. A value less than 1
@@ -2878,30 +2816,7 @@ class VirtualMachine(pulumi.CustomResource):
                  args: VirtualMachineArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        ## 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 `Hard Disk`, 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 `Hard Disk 0`, a disk on the same controller with a unit number of `1` would be `Hard Disk 1`, but the next disk, which is on SCSI controller `1` with a unit number of `0`, still becomes `Hard Disk 2`.
-        * 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.
+        Create a VirtualMachine resource with the given unique name, props, and options.
         :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.
@@ -2988,7 +2903,6 @@ class VirtualMachine(pulumi.CustomResource):
                  tools_upgrade_policy: Optional[pulumi.Input[str]] = None,
                  vapp: Optional[pulumi.Input[Union['VirtualMachineVappArgs', 'VirtualMachineVappArgsDict']]] = None,
                  vbs_enabled: Optional[pulumi.Input[bool]] = None,
-                 vtpm: Optional[pulumi.Input[Union['VirtualMachineVtpmArgs', 'VirtualMachineVtpmArgsDict']]] = None,
                  vvtd_enabled: Optional[pulumi.Input[bool]] = None,
                  wait_for_guest_ip_timeout: Optional[pulumi.Input[int]] = None,
                  wait_for_guest_net_routable: Optional[pulumi.Input[bool]] = None,
@@ -3075,7 +2989,6 @@ class VirtualMachine(pulumi.CustomResource):
             __props__.__dict__["tools_upgrade_policy"] = tools_upgrade_policy
             __props__.__dict__["vapp"] = vapp
             __props__.__dict__["vbs_enabled"] = vbs_enabled
-            __props__.__dict__["vtpm"] = vtpm
             __props__.__dict__["vvtd_enabled"] = vvtd_enabled
             __props__.__dict__["wait_for_guest_ip_timeout"] = wait_for_guest_ip_timeout
             __props__.__dict__["wait_for_guest_net_routable"] = wait_for_guest_net_routable
@@ -3183,7 +3096,6 @@ class VirtualMachine(pulumi.CustomResource):
             vbs_enabled: Optional[pulumi.Input[bool]] = None,
             vmware_tools_status: Optional[pulumi.Input[str]] = None,
             vmx_path: Optional[pulumi.Input[str]] = None,
-            vtpm: Optional[pulumi.Input[Union['VirtualMachineVtpmArgs', 'VirtualMachineVtpmArgsDict']]] = None,
             vvtd_enabled: Optional[pulumi.Input[bool]] = None,
             wait_for_guest_ip_timeout: Optional[pulumi.Input[int]] = None,
             wait_for_guest_net_routable: Optional[pulumi.Input[bool]] = None,
@@ -3284,7 +3196,6 @@ class VirtualMachine(pulumi.CustomResource):
         :param pulumi.Input[bool] vbs_enabled: Flag to specify if Virtualization-based security is enabled for this virtual machine.
         :param pulumi.Input[str] vmware_tools_status: The state of  VMware Tools in the guest. This will determine the proper course of action for some device operations.
         :param pulumi.Input[str] vmx_path: The path of the virtual machine configuration file on the datastore in which the virtual machine is placed.
-        :param pulumi.Input[Union['VirtualMachineVtpmArgs', 'VirtualMachineVtpmArgsDict']] vtpm: A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
         :param pulumi.Input[bool] vvtd_enabled: Flag to specify if I/O MMU virtualization, also called Intel Virtualization Technology for Directed I/O (VT-d) and AMD
                I/O Virtualization (AMD-Vi or IOMMU), is enabled.
         :param pulumi.Input[int] wait_for_guest_ip_timeout: The amount of time, in minutes, to wait for an available IP address on this virtual machine. A value less than 1
@@ -3380,7 +3291,6 @@ class VirtualMachine(pulumi.CustomResource):
         __props__.__dict__["vbs_enabled"] = vbs_enabled
         __props__.__dict__["vmware_tools_status"] = vmware_tools_status
         __props__.__dict__["vmx_path"] = vmx_path
-        __props__.__dict__["vtpm"] = vtpm
         __props__.__dict__["vvtd_enabled"] = vvtd_enabled
         __props__.__dict__["wait_for_guest_ip_timeout"] = wait_for_guest_ip_timeout
         __props__.__dict__["wait_for_guest_net_routable"] = wait_for_guest_net_routable
@@ -4042,14 +3952,6 @@ class VirtualMachine(pulumi.CustomResource):
         """
         return pulumi.get(self, "vmx_path")
-    @property
-    @pulumi.getter
-    def vtpm(self) -> pulumi.Output[Optional['outputs.VirtualMachineVtpm']]:
-        """
-        A specification for a virtual Trusted Platform Module (TPM) device on the virtual machine.
-        """
-        return pulumi.get(self, "vtpm")
     @property
     @pulumi.getter(name="vvtdEnabled")
     def vvtd_enabled(self) -> pulumi.Output[Optional[bool]]:

pulumi_vsphere/virtual_machine_class.py CHANGED Viewed

@@ -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__ = ['VirtualMachineClassArgs', 'VirtualMachineClass']

pulumi_vsphere/virtual_machine_snapshot.py CHANGED Viewed

@@ -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__ = ['VirtualMachineSnapshotArgs', 'VirtualMachineSnapshot']

pulumi_vsphere/vm_storage_policy.py CHANGED Viewed

@@ -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 *

pulumi_vsphere/vmfs_datastore.py CHANGED Viewed

@@ -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__ = ['VmfsDatastoreArgs', 'VmfsDatastore']
@@ -466,139 +461,7 @@ class VmfsDatastore(pulumi.CustomResource):
                  tags: Optional[pulumi.Input[Sequence[pulumi.Input[str]]]] = None,
                  __props__=None):
         """
-        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
+        Create a VmfsDatastore 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[Mapping[str, pulumi.Input[str]]] custom_attributes: Map of custom attribute ids to attribute
@@ -636,139 +499,7 @@ class VmfsDatastore(pulumi.CustomResource):
                  args: VmfsDatastoreArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        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
+        Create a VmfsDatastore resource with the given unique name, props, and options.
         :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 CHANGED Viewed

@@ -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 *
@@ -438,18 +433,13 @@ class Vnic(pulumi.CustomResource):
             ])
         ```
-        ## Import
-        An existing vNic can be imported into this resource
+        ## Importing
+        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.
@@ -540,18 +530,13 @@ class Vnic(pulumi.CustomResource):
             ])
         ```
-        ## Import
-        An existing vNic can be imported into this resource
+        ## Importing
+        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.0.dist-info → pulumi_vsphere-4.12.0a1725645004.dist-info}/METADATA RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pulumi_vsphere
-Version: 4.12.0
+Version: 4.12.0a1725645004
 Summary: A Pulumi package for creating vsphere resources
 License: Apache-2.0
 Project-URL: Homepage, https://pulumi.io
@@ -9,9 +9,8 @@ Keywords: pulumi,vsphere
 Requires-Python: >=3.8
 Description-Content-Type: text/markdown
 Requires-Dist: parver >=0.2.1
-Requires-Dist: pulumi <4.0.0,>=3.136.0
+Requires-Dist: pulumi <4.0.0,>=3.0.0
 Requires-Dist: semver >=2.8.1
-Requires-Dist: typing-extensions >=4.11 ; python_version < "3.11"
 [![Actions Status](https://github.com/pulumi/pulumi-vsphere/workflows/master/badge.svg)](https://github.com/pulumi/pulumi-vsphere/actions)
 [![Slack](http://www.pulumi.com/images/docs/badges/slack.svg)](https://slack.pulumi.com)

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

Potentially problematic release.

pulumi-vsphere 4.12.0py3-none-any.whl → 4.12.0a1725645004py3-none-any.whl