All Products
Search
Document Center

Microservices Engine:CloneNacosConfig

Last Updated:Apr 17, 2024

Clones an existing Nacos configuration from a namespace to another.

Operation description

mse-200-105

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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 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:CloneNacosConfigWrite
  • Cluster
    acs:mse:{#regionId}:{#accountId}:instance/{#InstanceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

The ID of the destination namespace.

mse_prepaid_public_cn-i7m25igg403
OriginNamespaceIdstringNo

The policy used when a write conflict occurs.

  • ABORT
  • SKIP
  • OVERWRITE
be821963-6d48-4ea5-9910-6057d****
TargetNamespaceIdstringNo

The IDs of configurations.

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

The language of the response. Valid values:

  • zh: Chinese
  • en: English
OVERWRITE
IdsstringYes

The data structure.

253661,253662
AcceptLanguagestringNo

The language of the response. Valid values:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

The ID of the request.

HttpStatusCodeinteger

Indicates whether the request was successful. Valid values:

  • true: The request was successful.
  • false: The request failed.
200
RequestIdstring

The error code returned if the request failed.

6678DBA9-5600-5948-ACF8-ED3105B288A3
Successboolean

The response code returned.

true
ErrorCodestring

The message returned.

mse-100-000
Codeinteger

The dynamic part in the error message. This parameter is used to replace the **%s** variable in the ErrMessage parameter.

Note If the return value of the ErrMessage parameter is The Value of Input Parameter %s is not valid and the return value of the DynamicMessage parameter is DtsJobId, the specified DtsJobId parameter is invalid.
200
Messagestring

The details of the data.

Clone Completed Successfully
DynamicMessagestring

The number of successful operations.

The specified parameter is invalid.
Dataobject

The number of skipped operations.

SuccCountinteger

The details of the skipped configurations.

100
SkipCountinteger

The data structure.

1
SkipDataobject []

The ID of the data.

DataIdstring

The details of the failed configurations.

test.yaml
Groupstring

The data structure.

public
FailDataobject []

The ID of the data.

DataIdstring

mse-200-105

test2.yaml
Groupstring

duplicatedClusterAliasName

test

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"
      }
    ]
  }
}

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
2023-04-25API Description Updatesee changesets
Change itemChange content
API DescriptionAPI Description Update.