All Products
Search
Document Center

Microservices Engine:CloneNacosConfig

Last Updated:May 08, 2025
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

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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 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
mse:CloneNacosConfigcreate
*All Resources
*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

Instance ID.

mse_prepaid_public_cn-i7m25igg403
OriginNamespaceIdstringNo

Source namespace ID.

be821963-6d48-4ea5-9910-6057d****
TargetNamespaceIdstringNo

Target namespace ID.

08be4b5d-2d1c-4e6e-aa85-83b9****
PolicystringYes

The strategy used when a write conflict occurs.

  • ABORT
  • SKIP
  • OVERWRITE
Enumeration Value:
  • ABORT: 终止.
  • OVERWRITE: 覆盖.
  • SKIP: 跳过.
OVERWRITE
IdsdeprecatedstringNo

List of configuration IDs.

253661,253662
DataIdsstringYes

Configuration items to be cloned, in the format of dataId+group, with multiple items separated by commas.

test+test,test1+test1
AcceptLanguagestringNo

Language type of the returned message:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

Data structure.

HttpStatusCodeinteger

HTTP status code.

200
RequestIdstring

Request ID.

6678DBA9-5600-5948-ACF8-ED3105B288A3
Successboolean

Request result, with the following values:

  • true: Request succeeded.
  • false: Request failed.
true
ErrorCodestring

Error code.

mse-100-000
Codeinteger

Response code.

200
Messagestring

Response message.

Clone Completed Successfully
DynamicMessagestring

Dynamic error message, used to replace the %s in the ErrMessage error message.

Note If ErrMessage returns The Value of Input Parameter %s is not valid, and DynamicMessage returns DtsJobId, it indicates that the input request parameter DtsJobId is invalid.
The specified parameter is invalid.
Dataobject

Data overview.

SuccCountinteger

Number of successes.

100
SkipCountinteger

Number of skips.

1
SkipDataarray<object>

Skipped configuration information.

SkipDataobject

Data structure.

DataIdstring

Data ID.

test.yaml
Groupstring

Group ID.

public
FailDataarray<object>

Failed configuration information.

FailDataobject
DataIdstring

Data ID.

test2.yaml
Groupstring

Group ID.

test
Reasonstring

The reason for the current operation.

param not support

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 codeError codeError messageDescription
400IllegalRequestInvalid request:%sInvalid request: %s
400InvalidParameterParameter error:%sRequest parameter error: %s
403NoPermissionYou are not authorized to perform this operation:%sYou do not have the permission to use this interface:%s
404NotFoundNot found:%sThe resource does not exist:%s
500InternalErrorConsole error. Try again later:%sConsole error. Try again later: %s

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

Change history

Change timeSummary of changesOperation
2024-08-01The request parameters of the API has changed. The response structure of the API has changedView Change Details
2023-04-25API Description UpdateView Change Details