DeleteVccGrantRule
If you delete a Lingjun HUB cross-account authorization that is connected to Lingjun, the related data is lost and cannot be recovered.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
eflo:DeleteVccGrantRule |
delete |
*VccGrantRule
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
Yes |
The region ID. |
cn-wulanchabu |
| GrantRuleId |
string |
Yes |
Authorization Entry ID |
grant-rule-jaj34d75h01 |
| InstanceId |
string |
No |
Network Instance ID |
vcc-cn-jaj34d75h01 |
| ErId |
string |
No |
Lingjun HUB 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.) |
Success |
| RequestId |
string |
Request ID of the current request |
BDBCC783-84CA-5733-8EEA-645C88B9009C |
| Content |
any |
Response body |
{} |
| AccessDeniedDetail |
string |
The details about the access denial. Note
This parameter is returned only if Resource Access Management (RAM) permission verification failed. |
None |
Examples
Success response
JSON format
{
"Code": 0,
"Message": "Success",
"RequestId": "BDBCC783-84CA-5733-8EEA-645C88B9009C",
"Content": "{}",
"AccessDeniedDetail": "None"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.