Deleting the nacos Namespace
Function
This API is used to delete the nacos namespace.
Authorization Information
- If you are using role/policy-based authorization, see the required permissions in Permissions and Supported Actions.
- If you are using identity policy-based authorization, the permission listed below is required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependency
cse:namespace:delete
write
engine
cse:namespace:write
-
URI
DELETE /v1/{project_id}/nacos/v1/console/namespaces
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID, which must be unique. The value contains 1 to 64 characters. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
namespace_id |
Yes |
String |
Namespace ID. |
Request
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
IAM token. |
|
x-engine-id |
Yes |
String |
Instance ID of an exclusive microservice engine. |
|
X-Enterprise-Project-ID |
Yes |
String |
Enterprise project ID. |
Response
Status code: 200
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
|
detail |
String |
Location details. |
Example Request
DELETE https://{endpoint}/v1/{project_id}/nacos/v1/console/namespaces
Example Response
true
Status Code
|
Status Code |
Description |
|---|---|
|
200 |
OK |
|
400 |
Bad Request |
Error Code
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot