vsphere-automation-vcenter 0.1.0 → 0.2.0

data/docs/VcenterVmStoragePolicyComplianceCheckSpec.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**vm_home** | **BOOLEAN** | Invoke compliance check on the virtual machine home directory if set to true. | 
+**vm_home** | **Boolean** | Invoke compliance check on the virtual machine home directory if set to true. | 
 **disks** | **Array<String>** | Identifiers of the virtual machine's virtual disks for which compliance should be checked. If unset or empty, compliance check is invoked on all the associated disks. When clients pass a value of this structure as a parameter, the field must contain identifiers for the resource type: vcenter.vm.hardware.Disk. When operations return a value of this structure as a result, the field will contain identifiers for the resource type: vcenter.vm.hardware.Disk. | [optional] 
 
 

data/docs/VcenterVmStoragePolicyComplianceInfoDisks.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmStoragePolicyComplianceVmComplianceInfo**](VcenterVmStoragePolicyComplianceVmComplianceInfo.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmStoragePolicyComplianceVmComplianceInfo**](VcenterVmStoragePolicyComplianceVmComplianceInfo.md) |  | [optional] 
 
 

data/docs/VcenterVmStoragePolicyUpdateSpecDisks.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmStoragePolicyDiskPolicySpec**](VcenterVmStoragePolicyDiskPolicySpec.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmStoragePolicyDiskPolicySpec**](VcenterVmStoragePolicyDiskPolicySpec.md) |  | [optional] 
 
 

data/docs/VcenterVmTemplateLibraryItemsCreateSpecDiskStorageOverrides.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmTemplateLibraryItemsCreateSpecDiskStorage**](VcenterVmTemplateLibraryItemsCreateSpecDiskStorage.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmTemplateLibraryItemsCreateSpecDiskStorage**](VcenterVmTemplateLibraryItemsCreateSpecDiskStorage.md) |  | [optional] 
 
 

data/docs/VcenterVmTemplateLibraryItemsDeploySpec.md

@@ -9,7 +9,7 @@ Name | Type | Description | Notes
 **disk_storage** | [**VcenterVmTemplateLibraryItemsDeploySpecDiskStorage**](VcenterVmTemplateLibraryItemsDeploySpecDiskStorage.md) |  | [optional] 
 **disk_storage_overrides** | **Array<Object>** | Storage specification for individual disks in the deployed virtual machine. This is specified as a mapping between disk identifiers in the source virtual machine template contained in the library item and their storage specifications. | [optional] 
 **placement** | [**VcenterVmTemplateLibraryItemsDeployPlacementSpec**](VcenterVmTemplateLibraryItemsDeployPlacementSpec.md) |  | [optional] 
-**powered_on** | **BOOLEAN** | Specifies whether the deployed virtual machine should be powered on after deployment. | [optional] 
+**powered_on** | **Boolean** | Specifies whether the deployed virtual machine should be powered on after deployment. | [optional] 
 **guest_customization** | [**VcenterVmTemplateLibraryItemsGuestCustomizationSpec**](VcenterVmTemplateLibraryItemsGuestCustomizationSpec.md) |  | [optional] 
 **hardware_customization** | [**VcenterVmTemplateLibraryItemsHardwareCustomizationSpec**](VcenterVmTemplateLibraryItemsHardwareCustomizationSpec.md) |  | [optional] 
 

data/docs/VcenterVmTemplateLibraryItemsDeploySpecDiskStorageOverrides.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmTemplateLibraryItemsDeploySpecDiskStorage**](VcenterVmTemplateLibraryItemsDeploySpecDiskStorage.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmTemplateLibraryItemsDeploySpecDiskStorage**](VcenterVmTemplateLibraryItemsDeploySpecDiskStorage.md) |  | [optional] 
 
 

data/docs/VcenterVmTemplateLibraryItemsHardwareCustomizationSpecDisksToUpdate.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmTemplateLibraryItemsDiskUpdateSpec**](VcenterVmTemplateLibraryItemsDiskUpdateSpec.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmTemplateLibraryItemsDiskUpdateSpec**](VcenterVmTemplateLibraryItemsDiskUpdateSpec.md) |  | [optional] 
 
 

data/docs/VcenterVmTemplateLibraryItemsHardwareCustomizationSpecNics.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmTemplateLibraryItemsEthernetUpdateSpec**](VcenterVmTemplateLibraryItemsEthernetUpdateSpec.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmTemplateLibraryItemsEthernetUpdateSpec**](VcenterVmTemplateLibraryItemsEthernetUpdateSpec.md) |  | [optional] 
 
 

data/docs/VcenterVmTemplateLibraryItemsInfoDisks.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmTemplateLibraryItemsDiskInfo**](VcenterVmTemplateLibraryItemsDiskInfo.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmTemplateLibraryItemsDiskInfo**](VcenterVmTemplateLibraryItemsDiskInfo.md) |  | [optional] 
 
 

data/docs/VcenterVmTemplateLibraryItemsInfoNics.md

@@ -3,7 +3,7 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**value** | [**VcenterVmTemplateLibraryItemsEthernetInfo**](VcenterVmTemplateLibraryItemsEthernetInfo.md) |  | [optional] 
 **key** | **String** |  | [optional] 
+**value** | [**VcenterVmTemplateLibraryItemsEthernetInfo**](VcenterVmTemplateLibraryItemsEthernetInfo.md) |  | [optional] 
 
 

data/docs/VchaCapabilitiesApi.md

@@ -16,6 +16,13 @@ Gets the capabilities of the active node of a VCHA cluster.
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaCapabilitiesApi.new
 
@@ -37,12 +44,12 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/VchaClusterActiveApi.md

@@ -4,11 +4,11 @@ All URIs are relative to *https://<vcenter>/rest*
 
 Method | HTTP request | Description
 ------------- | ------------- | -------------
-[**get**](VchaClusterActiveApi.md#get) | **POST** /vcenter/vcha/cluster/active?action=get | Retrieves information about the active node of a VCHA cluster.
+[**get**](VchaClusterActiveApi.md#get) | **POST** /vcenter/vcha/cluster/active | Retrieves information about the active node of a VCHA cluster.
 
 
 # **get**
-> VcenterVchaClusterActiveResult get(opts)
+> VcenterVchaClusterActiveResult get(action, opts)
 
 Retrieves information about the active node of a VCHA cluster.
 
@@ -16,15 +16,23 @@ Retrieves information about the active node of a VCHA cluster.
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterActiveApi.new
+action = 'action_example' # String | action=get
 opts = {
-  vcenter_vcha_cluster_active_get: VSphereAutomation::VcenterVchaClusterActiveGet.new # VcenterVchaClusterActiveGet | 
+  request_body: VCenter::VcenterVchaClusterActiveGet.new # VcenterVchaClusterActiveGet | 
 }
 
 begin
   #Retrieves information about the active node of a VCHA cluster.
-  result = api_instance.get(opts)
+  result = api_instance.get(action, opts)
   p result
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling VchaClusterActiveApi->get: #{e}"
@@ -35,7 +43,8 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **vcenter_vcha_cluster_active_get** | [**VcenterVchaClusterActiveGet**](VcenterVchaClusterActiveGet.md)|  | [optional] 
+ **action** | **String**| action=get | 
+ **request_body** | [**VcenterVchaClusterActiveGet**](VcenterVchaClusterActiveGet.md)|  | [optional] 
 
 ### Return type
 
@@ -43,12 +52,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/VchaClusterApi.md

@@ -4,14 +4,14 @@ All URIs are relative to *https://<vcenter>/rest*
 
 Method | HTTP request | Description
 ------------- | ------------- | -------------
-[**deploytask**](VchaClusterApi.md#deploytask) | **POST** /vcenter/vcha/cluster?action=deploy | Prepares, clones, and configures a VCHA cluster.
-[**failovertask**](VchaClusterApi.md#failovertask) | **POST** /vcenter/vcha/cluster?action=failover | Initiates failover from the active vCenter node to the passive node.   For forced failover, Active node immediately initiates a failover. This may result into a data loss after failover.    For planned failover, Active node flushes all the state to the Passive node, waits for the flush to complete before causing a failover. After the failover, Passive node starts without any data loss.    A failover is allowed only in the following cases:      1.  Cluster's mode is enabled and all cluster members are present.    2.  Cluster's mode is maintenance and all cluster members are present. 
+[**deploytask**](VchaClusterApi.md#deploytask) | **POST** /vcenter/vcha/cluster?action=deploy&vmw-task=true | Prepares, clones, and configures a VCHA cluster.
+[**failovertask**](VchaClusterApi.md#failovertask) | **POST** /vcenter/vcha/cluster | Initiates failover from the active vCenter node to the passive node.   For forced failover, Active node immediately initiates a failover. This may result into a data loss after failover.    For planned failover, Active node flushes all the state to the Passive node, waits for the flush to complete before causing a failover. After the failover, Passive node starts without any data loss.    A failover is allowed only in the following cases:      1.  Cluster's mode is enabled and all cluster members are present.    2.  Cluster's mode is maintenance and all cluster members are present. 
 [**get**](VchaClusterApi.md#get) | **POST** /vcenter/vcha/cluster?action=get | Retrieves the status of a VCHA cluster.
-[**undeploytask**](VchaClusterApi.md#undeploytask) | **POST** /vcenter/vcha/cluster?action=undeploy | Destroys the VCHA cluster and removes all VCHA specific information from the VCVA appliance. Optionally, the passive and witness node virtual machines will be deleted only if VCHA was deployed using automatic deployment. The active node in the cluster continues to run as a standalone VCVA appliance after the destroy operation has been performed.   If the VCHA cluster is in a transition state and not configured, then the VCHA cluster specific information is removed. 
+[**undeploytask**](VchaClusterApi.md#undeploytask) | **POST** /vcenter/vcha/cluster?action=undeploy&vmw-task=true | Destroys the VCHA cluster and removes all VCHA specific information from the VCVA appliance. Optionally, the passive and witness node virtual machines will be deleted only if VCHA was deployed using automatic deployment. The active node in the cluster continues to run as a standalone VCVA appliance after the destroy operation has been performed.   If the VCHA cluster is in a transition state and not configured, then the VCHA cluster specific information is removed. 
 
 
 # **deploytask**
-> VcenterVchaClusterDeployTaskResult deploytask(vcenter_vcha_cluster_deploy_task)
+> VcenterVchaClusterDeployTaskResult deploytask(request_body)
 
 Prepares, clones, and configures a VCHA cluster.
 
@@ -19,13 +19,20 @@ Prepares, clones, and configures a VCHA cluster.
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterApi.new
-vcenter_vcha_cluster_deploy_task = VSphereAutomation::VcenterVchaClusterDeployTask.new # VcenterVchaClusterDeployTask | 
+request_body = VCenter::VcenterVchaClusterDeployTask.new # VcenterVchaClusterDeployTask | 
 
 begin
   #Prepares, clones, and configures a VCHA cluster.
-  result = api_instance.deploytask(vcenter_vcha_cluster_deploy_task)
+  result = api_instance.deploytask(request_body)
   p result
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling VchaClusterApi->deploytask: #{e}"
@@ -36,7 +43,7 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **vcenter_vcha_cluster_deploy_task** | [**VcenterVchaClusterDeployTask**](VcenterVchaClusterDeployTask.md)|  | 
+ **request_body** | [**VcenterVchaClusterDeployTask**](VcenterVchaClusterDeployTask.md)|  | 
 
 ### Return type
 
@@ -44,17 +51,17 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **failovertask**
-> VcenterVchaClusterFailoverTaskResult failovertask(vcenter_vcha_cluster_failover_task)
+> VcenterVchaClusterFailoverTaskResult failovertask(action, request_body)
 
 Initiates failover from the active vCenter node to the passive node.   For forced failover, Active node immediately initiates a failover. This may result into a data loss after failover.    For planned failover, Active node flushes all the state to the Passive node, waits for the flush to complete before causing a failover. After the failover, Passive node starts without any data loss.    A failover is allowed only in the following cases:      1.  Cluster's mode is enabled and all cluster members are present.    2.  Cluster's mode is maintenance and all cluster members are present. 
 
@@ -62,13 +69,21 @@ Initiates failover from the active vCenter node to the passive node.   For force
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterApi.new
-vcenter_vcha_cluster_failover_task = VSphereAutomation::VcenterVchaClusterFailoverTask.new # VcenterVchaClusterFailoverTask | 
+action = 'action_example' # String | action=failover&vmw-task
+request_body = VCenter::VcenterVchaClusterFailoverTask.new # VcenterVchaClusterFailoverTask | 
 
 begin
   #Initiates failover from the active vCenter node to the passive node.   For forced failover, Active node immediately initiates a failover. This may result into a data loss after failover.    For planned failover, Active node flushes all the state to the Passive node, waits for the flush to complete before causing a failover. After the failover, Passive node starts without any data loss.    A failover is allowed only in the following cases:      1.  Cluster's mode is enabled and all cluster members are present.    2.  Cluster's mode is maintenance and all cluster members are present. 
-  result = api_instance.failovertask(vcenter_vcha_cluster_failover_task)
+  result = api_instance.failovertask(action, request_body)
   p result
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling VchaClusterApi->failovertask: #{e}"
@@ -79,7 +94,8 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **vcenter_vcha_cluster_failover_task** | [**VcenterVchaClusterFailoverTask**](VcenterVchaClusterFailoverTask.md)|  | 
+ **action** | **String**| action=failover&vmw-task | 
+ **request_body** | [**VcenterVchaClusterFailoverTask**](VcenterVchaClusterFailoverTask.md)|  | 
 
 ### Return type
 
@@ -87,12 +103,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
@@ -105,10 +121,17 @@ Retrieves the status of a VCHA cluster.
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterApi.new
 opts = {
-  vcenter_vcha_cluster_get: VSphereAutomation::VcenterVchaClusterGet.new # VcenterVchaClusterGet | 
+  request_body: VCenter::VcenterVchaClusterGet.new # VcenterVchaClusterGet | 
 }
 
 begin
@@ -124,7 +147,7 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **vcenter_vcha_cluster_get** | [**VcenterVchaClusterGet**](VcenterVchaClusterGet.md)|  | [optional] 
+ **request_body** | [**VcenterVchaClusterGet**](VcenterVchaClusterGet.md)|  | [optional] 
 
 ### Return type
 
@@ -132,17 +155,17 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **undeploytask**
-> VcenterVchaClusterUndeployTaskResult undeploytask(vcenter_vcha_cluster_undeploy_task)
+> VcenterVchaClusterUndeployTaskResult undeploytask(request_body)
 
 Destroys the VCHA cluster and removes all VCHA specific information from the VCVA appliance. Optionally, the passive and witness node virtual machines will be deleted only if VCHA was deployed using automatic deployment. The active node in the cluster continues to run as a standalone VCVA appliance after the destroy operation has been performed.   If the VCHA cluster is in a transition state and not configured, then the VCHA cluster specific information is removed. 
 
@@ -150,13 +173,20 @@ Destroys the VCHA cluster and removes all VCHA specific information from the VCV
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterApi.new
-vcenter_vcha_cluster_undeploy_task = VSphereAutomation::VcenterVchaClusterUndeployTask.new # VcenterVchaClusterUndeployTask | 
+request_body = VCenter::VcenterVchaClusterUndeployTask.new # VcenterVchaClusterUndeployTask | 
 
 begin
   #Destroys the VCHA cluster and removes all VCHA specific information from the VCVA appliance. Optionally, the passive and witness node virtual machines will be deleted only if VCHA was deployed using automatic deployment. The active node in the cluster continues to run as a standalone VCVA appliance after the destroy operation has been performed.   If the VCHA cluster is in a transition state and not configured, then the VCHA cluster specific information is removed. 
-  result = api_instance.undeploytask(vcenter_vcha_cluster_undeploy_task)
+  result = api_instance.undeploytask(request_body)
   p result
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling VchaClusterApi->undeploytask: #{e}"
@@ -167,7 +197,7 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **vcenter_vcha_cluster_undeploy_task** | [**VcenterVchaClusterUndeployTask**](VcenterVchaClusterUndeployTask.md)|  | 
+ **request_body** | [**VcenterVchaClusterUndeployTask**](VcenterVchaClusterUndeployTask.md)|  | 
 
 ### Return type
 
@@ -175,12 +205,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/VchaClusterDeploymentTypeApi.md

@@ -16,6 +16,13 @@ Retrieves the deployment type of a VCHA cluster.
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterDeploymentTypeApi.new
 
@@ -37,12 +44,12 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/VchaClusterModeApi.md

@@ -17,6 +17,13 @@ Retrieves the current mode of a VCHA cluster.
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterModeApi.new
 
@@ -38,17 +45,17 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **settask**
-> VcenterVchaClusterModeSetTaskResult settask(vcenter_vcha_cluster_mode_set_task)
+> VcenterVchaClusterModeSetTaskResult settask(vmw_task, request_body)
 
 Manipulates the mode of a VCHA Cluster. Following mode transitions are allowed:  enabled -> disabled - Allowed only in healthy and degraded states.  enabled -> maintenance - Allowed only in healthy state.  disabled -> enabled - Allowed only in healthy state.  maintenance -> enabled - Allowed only in healthy state with all nodes are running the same version.  maintenance -> disabled - Allowed only in healthy state with all nodes are running the same version.  All other transitions are not allowed.   VCHA Cluster configuration remains intact in any of the cluster modes. 
 
@@ -56,13 +63,21 @@ Manipulates the mode of a VCHA Cluster. Following mode transitions are allowed:
 ```ruby
 # load the gem
 require 'vsphere-automation-vcenter'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::VCenter::VchaClusterModeApi.new
-vcenter_vcha_cluster_mode_set_task = VSphereAutomation::VcenterVchaClusterModeSetTask.new # VcenterVchaClusterModeSetTask | 
+vmw_task = 'vmw_task_example' # String | vmw-task=true
+request_body = VCenter::VcenterVchaClusterModeSetTask.new # VcenterVchaClusterModeSetTask | 
 
 begin
   #Manipulates the mode of a VCHA Cluster. Following mode transitions are allowed:  enabled -> disabled - Allowed only in healthy and degraded states.  enabled -> maintenance - Allowed only in healthy state.  disabled -> enabled - Allowed only in healthy state.  maintenance -> enabled - Allowed only in healthy state with all nodes are running the same version.  maintenance -> disabled - Allowed only in healthy state with all nodes are running the same version.  All other transitions are not allowed.   VCHA Cluster configuration remains intact in any of the cluster modes. 
-  result = api_instance.settask(vcenter_vcha_cluster_mode_set_task)
+  result = api_instance.settask(vmw_task, request_body)
   p result
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling VchaClusterModeApi->settask: #{e}"
@@ -73,7 +88,8 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **vcenter_vcha_cluster_mode_set_task** | [**VcenterVchaClusterModeSetTask**](VcenterVchaClusterModeSetTask.md)|  | 
+ **vmw_task** | **String**| vmw-task=true | 
+ **request_body** | [**VcenterVchaClusterModeSetTask**](VcenterVchaClusterModeSetTask.md)|  | 
 
 ### Return type
 
@@ -81,12 +97,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json