After you delete a Lingjun HUB instance, the related data is lost and cannot be recovered.
Operation description
When you call this operation to delete the Lingjun HUB, note that:
-
Before you delete the instance, make sure that no network instance is connected to the Lingjun HUB instance.
-
After deletion, all related data is lost and cannot be recovered. Exercise caution when performing this operation.
-
This interface is an asynchronous interface. After this interface is called, the Lingjun HUB instance may not be deleted, and the system background deletion task is still in progress. You can call the ListErs or GetEr operation to query the deletion status of the Lingjun HUB.
If the status of the Lingjun HUB is Deleting, the Lingjun HUB instance is being deleted.
If no Lingjun HUB instance is recorded, the Lingjun HUB instance has been deleted.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
eflo:DeleteEr |
delete |
*Er
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
Yes |
The region ID. |
cn-wulanchabu |
| ErId |
string |
Yes |
Lingjun HUB Instance ID |
er-kkopgtne |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
AjaxResult |
||
| Code |
integer |
The response status code. |
0 |
| Message |
string |
The error message. (If the instance is in the Exception state, the exception cause is prompted.) |
成功 |
| RequestId |
string |
Request ID of the current request |
9C50C9CD-E799-54DA-BA7A-1FAF3DF80857 |
| Content |
any |
Response body |
{} |
| AccessDeniedDetail |
string |
The details about the access denial. |
{} |
Examples
Success response
JSON format
{
"Code": 0,
"Message": "成功",
"RequestId": "9C50C9CD-E799-54DA-BA7A-1FAF3DF80857",
"Content": "{}",
"AccessDeniedDetail": "{}"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.