This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.
Copy Nacos Configuration
Operation description
Note
This OpenAPI is not the Nacos-SDK API. For information related to the Nacos-SDK API, please refer to 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:
- For mandatory resource types, indicate with a prefix of * .
- 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:CloneNacosConfig | create | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| InstanceId | string | Yes | Instance ID. | mse_prepaid_public_cn-i7m25igg403 |
| OriginNamespaceId | string | No | Source namespace ID. | be821963-6d48-4ea5-9910-6057d**** |
| TargetNamespaceId | string | No | Target namespace ID. | 08be4b5d-2d1c-4e6e-aa85-83b9**** |
| Policy | string | Yes | The strategy used when a write conflict occurs.
Enumeration Value:
| OVERWRITE |
Idsdeprecated | string | No | List of configuration IDs. | 253661,253662 |
| DataIds | string | Yes | Configuration items to be cloned, in the format of dataId+group, with multiple items separated by commas. | test+test,test1+test1 |
| AcceptLanguage | string | No | Language type of the returned message:
| zh |
Response parameters
Examples
Sample success responses
JSONformat
{
"HttpStatusCode": 200,
"RequestId": "6678DBA9-5600-5948-ACF8-ED3105B288A3",
"Success": true,
"ErrorCode": "mse-100-000",
"Code": 200,
"Message": "Clone Completed Successfully",
"DynamicMessage": "The specified parameter is invalid.",
"Data": {
"SuccCount": 100,
"SkipCount": 1,
"SkipData": [
{
"DataId": "test.yaml",
"Group": "public "
}
],
"FailData": [
{
"DataId": "test2.yaml",
"Group": "test",
"Reason": "param not support"
}
]
}
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | IllegalRequest | Invalid request:%s | Invalid request: %s |
| 400 | InvalidParameter | Parameter error:%s | Request parameter error: %s |
| 403 | NoPermission | You are not authorized to perform this operation:%s | You do not have the permission to use this interface:%s |
| 404 | NotFound | Not found:%s | The resource does not exist:%s |
| 500 | InternalError | Console error. Try again later:%s | Console error. Try again later: %s |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-08-01 | The request parameters of the API has changed. The response structure of the API has changed | View Change Details |
| 2023-04-25 | API Description Update | View Change Details |
