All Products
Search
Document Center

Microservices Engine:CreateNacosConfig

Last Updated:Nov 20, 2024

Creates a Nacos configuration.

Operation description

Note The operation is not provided in Nacos SDKs. For information about Nacos SDKs, see 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:
    • 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:CreateNacosConfigget
*All Resources
*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

The ID of the instance.

mse_prepaid_public_cn-tl32****
DataIdstringYes

The ID of the data.

common.yaml
GroupstringYes

The ID of the group.

alime-bridge-aliyun
AppNamestringNo

The name of the application.

saledatacenter-task
TagsstringNo

The tags of the configuration.

Basic configurations
DescstringNo

The description of the configuration.

Basic module configuration.
TypestringNo

The format of the configuration. Supported formats include TEXT, JSON, and XML.

text
ContentstringNo

The content of the configuration.

asdf
NamespaceIdstringNo

The ID of the namespace.

547fd2a0-d0d6-****-80db2a1afb82
BetaIpsstringNo

The list of IP addresses where the beta release of the configuration is performed.

100.117.XX.XX,100.117.XX.XX
AcceptLanguagestringNo

The language of the response. Valid values:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

The data structure.

HttpCodestring

The HTTP status code.

202
RequestIdstring

The ID of the request.

673DBD43-569E-510F-B3DE-20BB8DFEB20A
Messagestring

The error message returned.

The request was successfully processed.
ErrorCodestring

The error code returned if the request failed.

mse-100-000
Codestring

The code returned.

1
Successboolean

Indicates whether the request was successful. Valid values:

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

Examples

Sample success responses

JSONformat

{
  "HttpCode": "202",
  "RequestId": "673DBD43-569E-510F-B3DE-20BB8DFEB20A",
  "Message": "The request was successfully processed.\n",
  "ErrorCode": "mse-100-000",
  "Code": "1",
  "Success": true
}

Error codes

HTTP status codeError codeError messageDescription
400duplicatedClusterAliasNameduplicated cluster alias nameThe instance name is duplicate. User another name.
400illegalRequestillegal request:%sInvalid request: %s
403NoPermissionYou are not authorized to perform this operation:%sYou do not have the permission to use this interface:%s
404clusterNotFoundcluster not foundThe cluster is not found.
500systemErrorsystem errorAn error occurred on the system. Try again later.

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

Change history

Change timeSummary of changesOperation
2024-10-28The internal configuration of the API is changed, but the call is not affectedView Change Details
2023-04-25API Description UpdateView Change Details