Delete a Configuration File (V2)
Function
Delete a configuration file.
Calling Method
For details, see Calling APIs.
URI
POST /v2.0/{project_id}/clusters/{cluster_id}/lgsconf/delete
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Definition: Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. Constraints: N/A Value range: Project ID of the account. Default value: N/A |
|
cluster_id |
Yes |
String |
Definition: ID of the cluster whose configuration file is to be deleted. For details about how to obtain the cluster ID, see Obtaining the Cluster ID. Constraints: N/A Value range: Cluster ID. Default value: N/A |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
name |
Yes |
String |
Configuration file name. |
Response Parameters
Status code: 200
Request succeeded.
None
Example Requests
Deleting a Configuration File
POST https://{Endpoint}/v2.0/{project_id}/clusters/5c2bab0d-ec5f-491f-9418-b8da38a26760/lgsconf/delete
{
"name" : "confName"
}
Example Responses
None
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
Request succeeded. |
|
400 |
The request is invalid. Do not retry the request without modifying it. |
|
409 |
The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exists, or the request failed to be processed because of the update of the conflict request. |
|
412 |
The server did not meet one of the preconditions contained in the request. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.