Detaches an access control policy.
Operation description
After you detach an access control policy, the operations performed on resources by using members are not limited by the policy. Make sure that the detached policy meets your expectations. Otherwise, your business may be affected.
Both the system and custom access control policies can be detached. If an object has only one access control policy attached, the policy cannot be detached.
Debugging
Authorization information
There is currently no authorization information disclosed in the API.
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
PolicyId | string | Yes | The ID of the access control policy. | cp-jExXAqIYkwHN**** |
TargetId | string | Yes | The ID of the object from which you want to detach the access control policy. Access control policies can be attached to the following objects:
| fd-ZDNPiT**** |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "9EA4F962-1A2E-4AFE-BE0C-B14736FC46CC"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | NotSupport.DetachLastControlPolicy | It is not detach the last control policy on the target node. | - |
404 | EntityNotExists.Target | The specified target does not exist in the resource directory. | The specified object does not exist in the resource directory. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|
No change history