Queries the historical details of Nacos configuration changes.
Operation description
Note
The operation is not provided in Nacos SDKs. For information about Nacos SDKs, see the official documentation.
Debugging
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 Resourcesis 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.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| mse:GetNacosHistoryConfig | get | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| InstanceId | string | Yes | The ID of the instance. | mse_prepaid_public_cn-st220g9ka02 |
| DataId | string | Yes | The ID of the data. | msg-center.main.yaml |
| Group | string | Yes | The name of the group. | DEFAULT_GROUP |
| NamespaceId | string | No | The ID of the namespace. | 6cf708a5-****-89f2-3ba62c5ee9ba |
| Nid | string | Yes | The version ID of the configuration. | 40**** |
| AcceptLanguage | string | No | The language of the response. Valid values:
| zh |
Response parameters
Examples
Sample success responses
JSONformat
{
"Message": "The request was successfully processed.\n",
"RequestId": "69AD2AA7-DB47-449B-941B-B14409DF****",
"Configuration": {
"AppName": "test",
"Md5": "23sdf32f****",
"DataId": "test.yaml",
"Content": "test",
"Group": "public",
"OpType": "text",
"EncryptedDataKey": "23fds****"
},
"ErrorCode": "NoPermission",
"Success": true
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | duplicatedClusterAliasName | duplicated cluster alias name | The instance name is duplicate. User another name. |
| 400 | illegalRequest | illegal request:%s | Invalid request: %s |
| 403 | NoPermission | You are not authorized to perform this operation:%s | You do not have the permission to use this interface:%s |
| 404 | clusterNotFound | cluster not found | The cluster is not found. |
| 500 | systemError | system error | An error occurred on the system. Try again later. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2023-04-25 | API Description Update | View Change Details |