chore: update product terms

Updates product terms to align with rebranding.

- vCenter Server >> vCenter
- vCenter Server instance >> vCenter instance
- ESXi >> ESX

Signed-off-by: Ryan Johnson <rya@tenthirtyam.org>

Author: tenthirtyam

.web-docs/README.md

@@ -39,7 +39,7 @@ packer plugins install github.com/hashicorp/vsphere
 
 - [vsphere-iso](/packer/integrations/hashicorp/vsphere/latest/components/builder/vsphere-iso) - This
   builder starts from an ISO file and uses the vSphere API to build a virtual machine image on
-  an ESXi host.
+  an ESX host.
 
 - [vsphere-clone](/packer/integrations/hashicorp/vsphere/latest/components/builder/vsphere-clone) -
   This builder clones a virtual machine from an existing template using the uses the vSphere API and
@@ -55,7 +55,7 @@ packer plugins install github.com/hashicorp/vsphere
   This post-processor uploads an artifact to a vSphere endpoint. The artifact must be a VMX, OVA,
   or OVF file.
 
-- [vsphere-template](/packer/integrations/hashicorp/vsphere/latest/components/post-processor/vsphere-template) - This post-processor uses an artifact from the `vmware-iso` builder with an ESXi host or an
+- [vsphere-template](/packer/integrations/hashicorp/vsphere/latest/components/post-processor/vsphere-template) - This post-processor uses an artifact from the `vmware-iso` builder with an ESX host or an
     artifact from the [vSphere](/packer/plugins/post-processors/vsphere/vsphere) post-processor. It
     then marks the virtual machine as a template and moves it to your specified path.
 
@@ -65,7 +65,7 @@ While both this plugin and the [`packer-plugin-vmware`](packer/integrations/hash
 designed to create virtual machine images, there are some key differences:
 
 - **Platforms**: This plugin is specifically developed to utilize the VMware vSphere API,
-  facilitating the creation of virtual machine images by integrating with VMware vCenter Server and
+  facilitating the creation of virtual machine images by integrating with VMware vCenter and
   the VMware vSphere Hypervisor. On the other hand, `packer-plugin-vmware` supports a variety of
   platforms including VMware vSphere Hypervisor and desktop virtualization products such as VMware
   Fusion, VMware Workstation, and VMware Player, though it does not utilize the vSphere API for its

.web-docs/components/builder/vsphere-clone/README.md

@@ -319,7 +319,7 @@ JSON Example:
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 
-- `tools_sync_time` (bool) - Enable time synchronization with the ESXi host where the virtual machine
+- `tools_sync_time` (bool) - Enable time synchronization with the ESX host where the virtual machine
   is running. Defaults to `false`.
 
 - `tools_upgrade_policy` (bool) - Automatically check for and upgrade VMware Tools after a virtual machine
@@ -923,14 +923,14 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter Server
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
   instance.
 
-- `username` (string) - The username to authenticate with the vCenter Server instance.
+- `username` (string) - The username to authenticate with the vCenter instance.
 
-- `password` (string) - The password to authenticate with the vCenter Server instance.
+- `password` (string) - The password to authenticate with the vCenter instance.
 
-- `insecure_connection` (bool) - Do not validate the certificate of the vCenter Server instance.
+- `insecure_connection` (bool) - Do not validate the certificate of the vCenter instance.
   Defaults to `false`.
 
   -> **Note:** This option is beneficial in scenarios where the certificate
@@ -1665,15 +1665,15 @@ The template is stored in an existing or newly created library item.
 
 - `cluster` (string) - The cluster where the VM template will be placed.
   If `cluster` and `resource_pool` are both specified, `resource_pool` must
-  belong to cluster. If `cluster` and `host` are both specified, the ESXi
+  belong to cluster. If `cluster` and `host` are both specified, the ESX
   host must be a member of the cluster. This option is not used when
   importing OVF templates. Defaults to [`cluster`](#cluster).
 
 - `folder` (string) - The virtual machine folder where the VM template will be placed.
   This option is not used when importing OVF templates. Defaults to
   the same folder as the source virtual machine.
 
-- `host` (string) - The ESXi host where the virtual machine template will be placed.
+- `host` (string) - The ESX host where the virtual machine template will be placed.
   If `host` and `resource_pool` are both specified, `resource_pool` must
   belong to host. If `host` and `cluster` are both specified, `host` must
   be a member of the cluster. This option is not used when importing OVF

.web-docs/components/builder/vsphere-iso/README.md

@@ -107,14 +107,14 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter Server
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
   instance.
 
-- `username` (string) - The username to authenticate with the vCenter Server instance.
+- `username` (string) - The username to authenticate with the vCenter instance.
 
-- `password` (string) - The password to authenticate with the vCenter Server instance.
+- `password` (string) - The password to authenticate with the vCenter instance.
 
-- `insecure_connection` (bool) - Do not validate the certificate of the vCenter Server instance.
+- `insecure_connection` (bool) - Do not validate the certificate of the vCenter instance.
   Defaults to `false`.
 
   -> **Note:** This option is beneficial in scenarios where the certificate
@@ -276,15 +276,15 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 <!-- Code generated from the comments of the CreateConfig struct in builder/vsphere/iso/step_create.go; DO NOT EDIT MANUALLY -->
 
 - `vm_version` (uint) - Specifies the virtual machine hardware version. Defaults to the most
-  current virtual machine hardware version supported by the ESXi host.
+  current virtual machine hardware version supported by the ESX host.
   Refer to [KB 315655](https://knowledge.broadcom.com/external/article?articleNumber=315655)
   for more information on supported virtual hardware versions.
 
 - `guest_os_type` (string) - The guest operating system identifier for the virtual machine.
   Defaults to `otherGuest`.
 
   To get a list of supported guest operating system identifiers for your
-  ESXi host, run the following PowerShell command using `VMware.PowerCLI`:
+  ESX host, run the following PowerShell command using `VMware.PowerCLI`:
 
   ```powershell
   Connect-VIServer -Server "vcenter.example.com" -User "administrator@vsphere.local" -Password "password"
@@ -1527,15 +1527,15 @@ The template is stored in an existing or newly created library item.
 
 - `cluster` (string) - The cluster where the VM template will be placed.
   If `cluster` and `resource_pool` are both specified, `resource_pool` must
-  belong to cluster. If `cluster` and `host` are both specified, the ESXi
+  belong to cluster. If `cluster` and `host` are both specified, the ESX
   host must be a member of the cluster. This option is not used when
   importing OVF templates. Defaults to [`cluster`](#cluster).
 
 - `folder` (string) - The virtual machine folder where the VM template will be placed.
   This option is not used when importing OVF templates. Defaults to
   the same folder as the source virtual machine.
 
-- `host` (string) - The ESXi host where the virtual machine template will be placed.
+- `host` (string) - The ESX host where the virtual machine template will be placed.
   If `host` and `resource_pool` are both specified, `resource_pool` must
   belong to host. If `host` and `cluster` are both specified, `host` must
   be a member of the cluster. This option is not used when importing OVF
@@ -1637,7 +1637,7 @@ JSON Example:
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 
-- `tools_sync_time` (bool) - Enable time synchronization with the ESXi host where the virtual machine
+- `tools_sync_time` (bool) - Enable time synchronization with the ESX host where the virtual machine
   is running. Defaults to `false`.
 
 - `tools_upgrade_policy` (bool) - Automatically check for and upgrade VMware Tools after a virtual machine
@@ -1756,10 +1756,10 @@ For example:
    `svc-packer-vsphere@example.com`), select the custom role (_e.g._ Packer to vSphere Integration
    Role) and the **Propagate to children** check box, and click **OK**.
 
-In an environment with many vCenter Server instances, such as management and workload, in enhanced
+In an environment with many vCenter instances, such as management and workload, in enhanced
 linked-mode, you may wish to further reduce the scope of access across the vSphere infrastructure if
-you do not want Packer to have access to the management vCenter Server instance, but only allow
-access to workload vCenter Server instances.
+you do not want Packer to have access to the management vCenter instance, but only allow
+access to workload vCenter instances.
 
 For example:
 

.web-docs/components/post-processor/vsphere-template/README.md

@@ -39,7 +39,7 @@ The following configuration options are available for the post-processor.
 - `insecure` (bool) - Skip the verification of the server certificate. Defaults to `false`.
 
 - `datacenter` (string) - The name of the datacenter to use.
-  Required when the vCenter Server instance endpoint has more than one datacenter.
+  Required when the vCenter instance has more than one datacenter.
 
 - `template_name` (string) - The name of the template.
   If not specified, the name of the virtual machine will be used.

.web-docs/components/post-processor/vsphere/README.md

@@ -23,16 +23,16 @@ The following configuration options are available for the post-processor.
 
 <!-- Code generated from the comments of the Config struct in post-processor/vsphere/post-processor.go; DO NOT EDIT MANUALLY -->
 
-- `cluster` (string) - The cluster or ESXi host to upload the virtual machine.
+- `cluster` (string) - The cluster or ESX host to upload the virtual machine.
   This can be either the name of the vSphere cluster or the fully qualified domain name (FQDN)
-  or IP address of the ESXi host.
+  or IP address of the ESX host.
 
 - `datacenter` (string) - The name of the vSphere datacenter object to place the virtual machine.
   This is _not required_ if `resource_pool` is specified.
 
 - `datastore` (string) - The name of the vSphere datastore to place the virtual machine.
 
-- `host` (string) - The fully qualified domain name or IP address of the vCenter Server or ESXi host.
+- `host` (string) - The fully qualified domain name or IP address of the vCenter instance or ESX host.
 
 - `password` (string) - The password to use to authenticate to the vSphere endpoint.
 
@@ -47,8 +47,8 @@ The following configuration options are available for the post-processor.
 
 - `disk_mode` (string) - The disk format of the target virtual machine. One of `thin`, `thick`,
 
-- `esxi_host` (string) - The fully qualified domain name or IP address of the ESXi host to upload the
-  virtual machine. This is _not required_ if `host` is a vCenter Server.
+- `esxi_host` (string) - The fully qualified domain name or IP address of the ESX host to upload the
+  virtual machine. This is _not required_ if `host` is a vCenter instance.
 
 - `insecure` (bool) - Skip the verification of the server certificate. Defaults to `false`.
 
@@ -77,7 +77,7 @@ The following configuration options are available for the post-processor.
   version, the deployed virtual machine's hardware version will be the same as the source
   virtual machine's.
 
-  This option is useful when deploying to vCenter Server instance ot an ESXi host whose
+  This option is useful when deploying to vCenter instance or an ESX host whose
   version is different than the one used to create the artifact.
 
   Refer to [KB 315655](https://knowledge.broadcom.com/external/article?articleNumber=315655)

builder/vsphere/common/step_config_params.go

@@ -47,7 +47,7 @@ type ConfigParamsConfig struct {
 	// are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
 	// in the vSphere API documentation.
 	ConfigParams map[string]string `mapstructure:"configuration_parameters"`
-	// Enable time synchronization with the ESXi host where the virtual machine
+	// Enable time synchronization with the ESX host where the virtual machine
 	// is running. Defaults to `false`.
 	ToolsSyncTime bool `mapstructure:"tools_sync_time"`
 	// Automatically check for and upgrade VMware Tools after a virtual machine

builder/vsphere/common/step_connect.go

@@ -18,14 +18,14 @@ import (
 )
 
 type ConnectConfig struct {
-	// The fully qualified domain name or IP address of the vCenter Server
+	// The fully qualified domain name or IP address of the vCenter instance
 	// instance.
 	VCenterServer string `mapstructure:"vcenter_server"`
-	// The username to authenticate with the vCenter Server instance.
+	// The username to authenticate with the vCenter instance.
 	Username string `mapstructure:"username"`
-	// The password to authenticate with the vCenter Server instance.
+	// The password to authenticate with the vCenter instance.
 	Password string `mapstructure:"password"`
-	// Do not validate the certificate of the vCenter Server instance.
+	// Do not validate the certificate of the vCenter instance.
 	// Defaults to `false`.
 	//
 	// -> **Note:** This option is beneficial in scenarios where the certificate

builder/vsphere/common/step_import_to_content_library.go

@@ -44,15 +44,15 @@ type ContentLibraryDestinationConfig struct {
 	Description string `mapstructure:"description"`
 	// The cluster where the VM template will be placed.
 	// If `cluster` and `resource_pool` are both specified, `resource_pool` must
-	// belong to cluster. If `cluster` and `host` are both specified, the ESXi
+	// belong to cluster. If `cluster` and `host` are both specified, the ESX
 	// host must be a member of the cluster. This option is not used when
 	// importing OVF templates. Defaults to [`cluster`](#cluster).
 	Cluster string `mapstructure:"cluster"`
 	// The virtual machine folder where the VM template will be placed.
 	// This option is not used when importing OVF templates. Defaults to
 	// the same folder as the source virtual machine.
 	Folder string `mapstructure:"folder"`
-	// The ESXi host where the virtual machine template will be placed.
+	// The ESX host where the virtual machine template will be placed.
 	// If `host` and `resource_pool` are both specified, `resource_pool` must
 	// belong to host. If `host` and `cluster` are both specified, `host` must
 	// be a member of the cluster. This option is not used when importing OVF

builder/vsphere/driver/resource_pool_test.go

@@ -30,7 +30,7 @@ func TestVCenterDriver_FindResourcePool(t *testing.T) {
 }
 
 func TestVCenterDriver_FindResourcePoolStandaloneESX(t *testing.T) {
-	// Standalone ESXi host without a vCenter Server instance
+	// Standalone ESX host without a vCenter instance
 	model := simulator.ESX()
 	defer model.Remove()
 

builder/vsphere/iso/step_create.go

@@ -84,15 +84,15 @@ type NIC struct {
 
 type CreateConfig struct {
 	// Specifies the virtual machine hardware version. Defaults to the most
-	// current virtual machine hardware version supported by the ESXi host.
+	// current virtual machine hardware version supported by the ESX host.
 	// Refer to [KB 315655](https://knowledge.broadcom.com/external/article?articleNumber=315655)
 	// for more information on supported virtual hardware versions.
 	Version uint `mapstructure:"vm_version"`
 	// The guest operating system identifier for the virtual machine.
 	// Defaults to `otherGuest`.
 	//
 	// To get a list of supported guest operating system identifiers for your
-	// ESXi host, run the following PowerShell command using `VMware.PowerCLI`:
+	// ESX host, run the following PowerShell command using `VMware.PowerCLI`:
 	//
 	// ```powershell
 	// Connect-VIServer -Server "vcenter.example.com" -User "administrator@vsphere.local" -Password "password"