Creates a tag policy.
Operation description
This topic provides an example on how to call the API operation to create a tag policy named test
. In this example, the Tag Policy feature in multi-account mode is used. The tag policy defines that resources to which the CostCenter:Beijing
or CostCenter:Shanghai
tag is added are compliant and other resources are not compliant.
Debugging
Authorization information
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | No | The region ID. Set the value to cn-shanghai. | cn-shanghai |
PolicyName | string | Yes | The name of the tag policy. The name must be 1 to 128 characters in length and can contain letters, digits, and underscores (_). | test |
PolicyDesc | string | No | The description of the tag policy. The description must be 0 to 512 characters in length. | This is a tag policy example. |
PolicyContent | string | Yes | The document of the tag policy. For more information about the syntax of a tag policy, see Syntax of a tag policy. | {"tags":{"CostCenter":{"tag_value":{"@@assign":["Beijing","Shanghai"]},"tag_key":{"@@assign":"CostCenter"}}}} |
DryRun | boolean | No | Specifies whether to perform only a dry run, without performing the actual request. Valid values:
| false |
UserType | string | No | The mode of the Tag Policy feature. Valid values:
For more information about the modes of the Tag Policy feature, see Modes of the Tag Policy feature. | RD |
For more information about common request parameters, see Common parameters.
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "FDBE270D-C491-5EEC-A5CD-98245422D3F7",
"PolicyId": "p-5732750813924f90****",
"PolicyName": "test"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||
---|---|---|---|---|
2023-12-08 | The response structure of the API has changed | see changesets | ||
|