Help Center/ Cloud Search Service/ API Reference/ API V2/ Logstash/ Delete a Configuration File (V2)

Updated on 2026-01-09 GMT+08:00

CLI Examples

View PDF

Delete a Configuration File (V2)

Delete a configuration file.

For details, see Calling APIs.

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.

If you are using identity policy-based authorization, the following identity policy-based permissions are required.

Action	Access Level	Resource Type (*: required)	Condition Key	Alias	Dependencies
css:logstash:confDelete	Write	cluster *	g:EnterpriseProjectId g:ResourceTag/<tag-key>	-	-

POST /v2.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

Deleting a Configuration File

POST https://{Endpoint}/v2.0/{project_id}/clusters/5c2bab0d-ec5f-491f-9418-b8da38a26760/lgsconf/delete

{
  "name" : "confName"
}

None

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.