All Products
Search
Document Center

PolarDB:UntagResources

Last Updated:Oct 10, 2024

Unbinds tags from PolarDB clusters.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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:
    • The required resource types are displayed in bold characters.
    • 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.
OperationAccess levelResource typeCondition keyAssociated operation
polardb:UntagResourcesdelete
  • DBCluster
    acs:polardb:{#regionId}:{#accountId}:dbcluster/{#DbClusterId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The ID of the region.

Note You can call the DescribeRegions operation to query the available regions.
cn-hangzhou
ResourceTypestringYes

The type of the resource. Set the value to cluster.

cluster
AllbooleanNo

Specifies whether to detach all tags from the cluster. Valid values: true and false. Default value: false.

Note This parameter takes effect only if TagKey.n is empty.
true
ResourceIdarrayYes

The IDs of the clusters.

stringYes

The ID of the cluster. To unbind tags from multiple clusters at the same time, click Add to add cluster IDs.

Note You can unbind tags from up to 50 clusters at the same time.
pc-***************
TagKeyarrayNo

The keys of the tags.

stringNo

The key of the tag. To unbind multiple tags from a cluster at the same time, click Add to add tag keys.

Note You can unbind up to 20 tag keys at the same time.
type

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

2D69A58F-345C-4FDE-88E4-BF5189******

Examples

Sample success responses

JSONformat

{
  "RequestId": "2D69A58F-345C-4FDE-88E4-BF5189******"
}

Error codes

HTTP status codeError codeError messageDescription
400NumberExceed.TagsThe Tags parameter`s number is exceed.The maximum number of tags is reached.
400InvalidTagKey.MalformedThe specified parameter TagKey.n is not valid.The specified TagKey.n parameter is invalid.
400InvalidParameter.TagKeysOrAllThe specified parameter TagKeys or All is not valid.The parameter of the key of the tag or the parameter of whether to delete all tags of the resource is invalid.
404InvalidDBClusterId.NotFoundThe DBInstanceId provided does not exist in our records.The specified DBClusterId parameter does not exist in the current record.

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

Change history

Change timeSummary of changesOperation
2024-05-23The Error code has changedView Change Details
2023-09-12The Error code has changedView Change Details