Esx. Settings. Depots. Umds Delete
The task-based delete operation removes content of the UMDS depot from vLCM completely. Note: The non task-based 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.
This operation was added in vSphere API 7.0.0.0.
Returns an authorization error if you do not have all of the privileges described as follows:
- Operation execution requires VcIntegrity.lifecycleDepots.Delete.
Success!
If the content of UMDS depot to be deleted is used in some baseline or desired state. The value of the data property of Vapi.Std.Errors.Error will be the PrecheckResult schema that lists the information of affected baselines and desired states. This error is applicable to the task-based delete operation only.
"Vapi.Std.Errors.ResourceInUse Object"
If the caller is not authenticated.
"Vapi.Std.Errors.Unauthenticated Object"
If there is no UMDS depot configured in the system.
"Vapi.Std.Errors.NotFound Object"
If there some unknown internal error. The accompanying error message will give more details about the failure. For task-based 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 property of Vapi.Std.Errors.Error will be the DeleteResult schema that lists all the errors encountered.
"Vapi.Std.Errors.Error Object"
If the service is not available.
"Vapi.Std.Errors.ServiceUnavailable Object"
curl -X DELETE -H 'Authorization: <value>' https://{api_host}/esx/settings/depots/umds