Cluster Profile Update Cluster Profile
Update the ClusterProfile with the specified config.
Required privileges: Profile.Edit
The unique identifier for the managed object to which the method attaches; the serialized managed object reference for a request has the form moType/moId, in this case ClusterProfile/{moId}.
The vSphere release schema. The current specification covers vSphere 8.0.2.0 APIs.
{
"config": {
"_typeName": "string",
"name": "string",
"annotation": "string",
"enabled": false
}
}DataObject which is a baseclass for other configuration specifications.
No Content
DuplicateName: If the profile with the new name already exists.
{
"_typeName": "string",
"faultCause": "MethodFault Object",
"faultMessage": [
{
"_typeName": "string",
"key": "string",
"arg": [
{
"_typeName": "string",
"key": "string",
"value": {
"_typeName": "string"
}
}
],
"message": "string"
}
],
"name": "string",
"object": {
"_typeName": "string",
"type": "string",
"value": "string"
}
}The name that is already bound in the name space.
The ManagedObjectReference data object type is a special-purpose data object. Commonly referred to as simply a "reference", "MoRef", "MOR", or other variations of this theme, instances of managed object references contain data that identifies specific server-side managed objects. Managed object references are typically one of the return types from a method invocation.
Managed object references are client application references to server-side managed objects. The client application uses ManagedObjectReference objects when it invokes operations on a server. A ManagedObjectReference is guaranteed to be unique and persistent during an object's lifetime. The reference persists after an object has moved within the inventory, across sessions, and across server restarts. If you remove an object, for example, a virtual machine, from the inventory, and then put it back, the reference changes.