Deleting a Configuration File

To delete a configuration file, you are advised to call the API for Deleting a Configuration File V2.

For details, see Calling APIs.

DELETE /v1.0/{project_id}/clusters/{cluster_id}/lgsconf/delete

**Table 1** Path Parameters
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

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
name	Yes	String	Configuration file name.

Status code: 200

Request succeeded.

None

Delete a configuration file.

DELETE https://{Endpoint}/v1.0/{project_id}/clusters/5c77b71c-5b35-4f50-8984-76387e42451a/lgsconf/delete

None

Status Code	Description
200	Request succeeded.
400	Invalid request. The client should modify the request instead of re-initiating 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 exits, or the requested update failed due to a conflict.
412	The server did not meet one of the preconditions contained in the request.

Parent topic: Logstash

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.