Esx Settings Clusters Configuration Drafts apply
Commit this draft and make it the new desired configuration for the cluster. The draft must be in the Esx Settings Clusters Configuration Drafts State.VALID state for this method to succeed. A successful commit will result in the draft being deleted. If the cluster is not empty, the Apply API will be called with the new desired state.
This operation was added in vSphere API 8.0.2.0.
Returns an authorization error if you do not have all of the privileges described as follows:
- Operation execution requires
VcIntegrity.ClusterConfiguration.Remediate. - The resource
ClusterComputeResourcereferenced by the parameter cluster requiresVcIntegrity.ClusterConfiguration.Remediate.
Identifier of the cluster
The parameter must be an identifier for the resource type: ClusterComputeResource.
Identifier of the working copy of the document.
The parameter must be an identifier for the resource type: com.vmware.esx.settings.draft.
Additional arguments for the operation.
{
"message": "string",
"apply_policy_spec": {
"failure_action": {
"action": "string",
"retry_delay": 0,
"retry_count": 0
},
"pre_remediation_power_action": "string",
"enable_quick_boot": false,
"disable_dpm": false,
"disable_hac": false,
"evacuate_offline_vms": false,
"enforce_hcl_validation": false,
"parallel_remediation_action": {
"enabled": false,
"max_hosts": 0
},
"enforce_quick_patch": false,
"config_manager_policy_spec": {
"serial_remediation": false
}
}
}Message to include with the commit.
This property was added in vSphere API 8.0.2.0.
If missing or null, message is set to empty string.
The parameter can be used to override the default remediation policies for the apply task.
This property was added in vSphere API 8.0.2.0.
if missing or null the default cluster remediation policies are used.
A structure that contains the ID of the new commit and, if an ApplySpec was supplied, the ID of the Apply task.
"Esx Settings Clusters Configuration Drafts ApplyResult Object"The ID of the commit created for this operation.
This property was added in vSphere API 8.0.2.0.
When clients pass a value of this schema as a parameter, the property must be an identifier for the resource type: com.vmware.esx.settings.commit. When operations return a value of this schema as a response, the property will be an identifier for the resource type: com.vmware.esx.settings.commit.
If the cluster is not empty, this will be set to the ID of the Apply task.
This property was added in vSphere API 8.0.2.0.
When clients pass a value of this schema as a parameter, the property must be an identifier for the resource type: com.vmware.cis.task. When operations return a value of this schema as a response, the property will be an identifier for the resource type: com.vmware.cis.task.
If the draft is not in the Esx Settings Clusters Configuration Drafts State.VALID state.
"Vapi Std Errors NotAllowedInCurrentState Object"If the caller is not authenticated.
"Vapi Std Errors Unauthenticated Object"Indicates the authentication challenges applicable to the target API provider. It can be used by a client to discover the correct authentication scheme to use. The exact syntax of the value is defined by the specific provider, the protocol and authentication schemes used.
For example, a provider using REST may adhere to the WWW-Authenticate HTTP header specification, RFC7235, section 4.1. In this case an example challenge value may be: SIGN realm="27da1358-2ba4-11e9-b210-d663bd873d93",sts="http://vcenter/sso?vsphere.local", Basic realm="vCenter"
This property was added in vSphere API 7.0.0.0.
This property is optional because it was added in a newer version than its parent node.
If there is no cluster associated with cluster or no draft associated with draft in the system.
"Vapi Std Errors NotFound Object"If there is unknown internal error. The accompanying error message will give more details about the failure.
"Vapi Std Errors Error Object"Stack of one or more localizable messages for human error consumers.
The message at the top of the stack (first in the list) describes the error from the perspective of the operation the client invoked.
Each subsequent message in the stack describes the "cause" of the prior message.
Data to facilitate clients responding to the operation reporting a standard error to indicating that it was unable to complete successfully.
Operations may provide data that clients can use when responding to errors. Since the data that clients need may be specific to the context of the operation reporting the error, different operations that report the same error may provide different data in the error. The documentation for each each operation will describe what, if any, data it provides for each error it reports.
The Vapi Std Errors ArgumentLocations, Vapi Std Errors FileLocations, and Vapi Std Errors TransientIndication schemas are intended as possible values for this property. Vapi Std DynamicID may also be useful as a value for this property (although that is not its primary purpose). Some resources may provide their own specific schemas for use as the value of this property when reporting errors from their operations.
Some operations will not set this property when reporting errors.
Discriminator field to help API consumers identify the structure type.
For more information see: Vapi Std Errors Error Type.
This property was added in vSphere API 6.7.2.
Can be missing or null for compatibility with preceding implementations.
If the service is not available.
"Vapi Std Errors ServiceUnavailable Object" curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{}' https://{api_host}/api/esx/settings/clusters/{cluster}/configuration/drafts/{draft}?action=apply