Delete Depots UMDs Task
The task-based Umds.delete operation removes content of the UMDS depot from vLCM completely. Note: The non task-based Umds.delete operation has been deprecated. It deletes only the record of UMDS depot from database, instead of removing the content of UMDS depot from vLCM. if you do not have all of the privileges described as follows: - Operation execution requires VcIntegrity.lifecycleDepots.Delete.
Required session ID, acquired from Create Session API under CIS product
An identifier for the task created by this API invocation will be returned. If the non-async version of the operation returns a value, this id can be used with the CIS Get Task operation to fetch that value. The normal description of this operation’s return value will follow if one exists.
com.vmware.vapi.std.errors.resource_in_use : If the content of UMDS depot to be deleted is used in some baseline or desired state. The value of the data field of Error will be the PrecheckResult structure that lists the information of affected baselines and desired states. This error is applicable to the task-based Umds.delete operation only.
com.vmware.vapi.std.errors.unauthenticated : If the caller is not authenticated.
com.vmware.vapi.std.errors.not_found : If there is no UMDS depot configured in the system.
com.vmware.vapi.std.errors.error : If there some unknown internal error. The accompanying error message will give more details about the failure. For task-based Umds.delete operation, once the task is started, it does NOT stop if encountering an error. Instead, it will continuously run to completion. In this case, the value of the data field of Error will be the DeleteResult structure that lists all the errors encountered.
com.vmware.vapi.std.errors.service_unavailable : If the service is not available.
‘Default’ means this response is used for all HTTP codes that are not covered individually for this operation.
PowerCLI Client SDK Example