DeleteNacosConfig - Microservices Engine - Alibaba Cloud Documentation Center

This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Delete specified Nacos configuration

Operation description

Note The current OpenAPI is not the Nacos-SDK API. For information related to the Nacos-SDK API, please refer to the official documentation.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
mse:DeleteNacosConfig	delete	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	Instance ID.	mse_prepaid_public_cn-tl32epfyu18
DataId	string	Yes	Configuration ID.	user-ds.yml
Group	string	Yes	Group type.	HALVIE_MICRO_GROUP
NamespaceId	string	No	Namespace ID. Default is public.	0e9d849b-****-8435da6c21ad
Beta	boolean	No	Whether it is a Beta release. Default is false. `true`: Yes `false`: No	true
AcceptLanguage	string	No	Language type of the returned information: zh: Chinese en: English	zh

Response parameters

Parameter	Type	Description	Example
	object	Data structure.
HttpCode	string	HTTP status code.	202
RequestId	string	Request ID.	4FEFC13F-EB50-51E1-97D8-C5CBA8CD1B84
Message	string	Message.	success
ErrorCode	string	Error code.	mse-100-000
Code	string	Return code.	200
Success	boolean	Request result, with the following values: - `true`: The request was successful. - `false`: The request failed.	true

Examples

Sample success responses

JSONformat

{
  "HttpCode": 202,
  "RequestId": "4FEFC13F-EB50-51E1-97D8-C5CBA8CD1B84",
  "Message": "success",
  "ErrorCode": "mse-100-000",
  "Code": 200,
  "Success": true
}

Error codes

HTTP status code	Error code	Error message	Description
400	IllegalRequest	Invalid request:%s	Invalid request: %s
400	InvalidParameter	Parameter error:%s	Request parameter error: %s
403	NoPermission	You are not authorized to perform this operation:%s	You do not have the permission to use this interface:%s
404	NotFound	Not found:%s	The resource does not exist:%s
500	InternalError	Console error. Try again later:%s	Console error. Try again later: %s

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2023-04-25	The internal configuration of the API is changed, but the call is not affected	View Change Details