Deleting Scheduled CU Changes in Batches (Discarded)¶
Function¶
This API is used to delete scheduled CU changes in batches.
Note
This API has been discarded and is not recommended.
URI¶
URI format
POST /v1/{project_id}/queues/{queue_name}/plans/batch-delete
Parameter description
Table 1 URI parameters¶ Parameter
Mandatory
Type
Description
project_id
Yes
String
Project ID, which is used for resource isolation. For details about how to obtain its value, see Obtaining a Project ID.
queue_name
Yes
String
Name of the queue for which the scheduled CU change is to be deleted. The name contains 1 to 128 characters. Use commas (,) to separate multiple queue names.
Request¶
Parameter | Mandatory | Type | Description |
|---|---|---|---|
plan_ids | Yes | Array of Long | Scaling policy IDs of the queues you want to delete. For details, see Viewing a Scheduled CU Change (Discarded). Example: "plan_ids": [8,10] |
Response¶
Parameter | Mandatory | Type | Description |
|---|---|---|---|
is_success | No | Boolean | Indicates whether the request is successfully executed. Value true indicates that the request is successfully executed. |
message | No | String | System prompt. If execution succeeds, the parameter setting may be left blank. |
Example Request¶
Delete the scaling plans whose IDs are 3 and 4.
{
"plan_ids": [3,4]
}
Example Response¶
{
"is_success": true,
"message": ""
}
Status Codes¶
Table 4 describes status codes.
Status Code | Description |
|---|---|
200 | Deletion succeeded. |
400 | Request failure. |
500 | Internal service error. |
Error Codes¶
If an error occurs when this API is invoked, the system does not return the result similar to the preceding example, but returns the error code and error information. For details, see Error Codes.
Error Code | Error Message |
|---|---|
DLI.0002 | The plans with id 8, 9 do not exist. |