DeleteLoadBalancer
Delete one or more specified CLB instances. After successful deletion, the listeners and forwarding rules under the CLB instance will be deleted together, and the backend service will be unbound.
Wire call
Converge Cloud is RPC over HTTP. There is one path — / — and the action travels in the X-TC-Action header. The /clb/DeleteLoadBalancer path used in the OpenAPI document is a documentation convenience so each action is addressable; it is not a route on the server.
curl -sS https://clb.api3.convergecloud.com/ \
-H 'Authorization: TC3-HMAC-SHA256 Credential=<SecretId>/<YYYY-MM-DD>/clb/tc3_request, SignedHeaders=content-type;host;x-tc-action, Signature=<sig>' \
-H 'Content-Type: application/json; charset=utf-8' \
-H 'Host: clb.api3.convergecloud.com' \
-H 'X-TC-Action: DeleteLoadBalancer' \
-H 'X-TC-Version: 2018-03-17' \
-H 'X-TC-Timestamp: <unix-seconds>' \
-H 'X-TC-Region: luzon' \
-d '{"LoadBalancerIds":["<LoadBalancerId>"]}'Request parameters
| Field | Type | Required | Description |
|---|---|---|---|
| LoadBalancerIds | string[] | Yes | CLB instance ID array to be deleted, which can be obtained by calling the DescribeLoadBalancers API. The array can include up to 20 elements. |
| ForceDelete | boolean | No | Whether to forcibly delete the CLB instance. True indicates forced deletion; False indicates non-forced deletion, and blocking verification is required. |
Response
Fields are returned inside the Response envelope. Converge Cloud answers HTTP 200 for errors as well as successes, so read Response.Error rather than the status code — and test for the presence of that object, because Code is occasionally the empty string.
| Field | Type | Description |
|---|---|---|
| RequestId | string | The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem. |
{
"Response": {
// action-specific fields,
"RequestId": "…"
}
}{
"Response": {
"Error": { "Code": "…", "Message": "…" },
"RequestId": "…"
}
}Try it
What failure looks like
Example error responses for this action. Match on Code.
{
"Response": {
"Error": {
"Code": "InvalidParameter.LBIdNotFound",
"Message": "Some loadBalancer not exist"
},
"RequestId": "0eeae055-5574-e006-61c5-bea14ee80ae2"
}
}Behaviour
Read back with DescribeLoadBalancers; a successful response does not guarantee the load balancer was deleted.
