Generates a resource non-compliance report.
Operation description
If you use the Tag Policy feature in single-account mode, you can call this API operation to generate a resource non-compliance report for the current logon account. If you use the Tag Policy feature in multi-account mode, you can call this API operation to generate a resource non-compliance report for the Root folder, a folder other than the Root folder, or a member in a resource directory. For more information about the modes of the Tag Policy feature, see Modes of the Tag Policy feature.
This topic provides an example on how to call this API operation to generate a resource non-compliance report for the current logon account. In this example, the Tag Policy feature in single-account mode is used.
Debugging
Authorization information
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | No | The region ID. Set the value to cn-shanghai. | cn-shanghai |
TargetId | string | No | The ID of the object. | 154950938137**** |
TargetType | string | No | The type of the object. Valid values:
Note
The value of this parameter is not case-sensitive.
| ACCOUNT |
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. Note
This parameter is required if the management account of your resource directory is used to enable the Tag Policy feature in both single-account mode and multi-account mode. The value of this parameter is not case-sensitive.
| USER |
For more information about common request parameters, see Common parameters.
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "37B2AC06-89D8-5D95-98DF-3E68C12BDE05",
"ReportId": "crp-ao0786618088006c****"
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | GlobalAggregator.NotFount | Can not find global aggregator |
403 | NoPermission.Operator | Only the RD admin account has permission to operate |
403 | TagPolicy.NotOpen | You have not activated the tag policy service. |
403 | TagPolicy.PendingEnable | The tag policy status is pending enable. |
403 | WrongEndpoint | Only the shanghai endpoint supports the operation. |
For a list of error codes, visit the Service error codes.