All Products
Search
Document Center

Microservices Engine:GetNacosConfig

Last Updated:Mar 06, 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.

Get 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:GetNacosConfigget
*EngineNamespace
acs:mse:{#regionId}:{#accountId}:instance/{#InstanceId}/{#NamespaceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

Instance ID.

mse-cn-i7m2h0****
DataIdstringYes

Data ID.

halvie-mp-item****
GroupstringYes

Configuration group information.

common
NamespaceIdstringNo

Namespace ID.

ddaf8f12-****-b1c1-86e7c72e266b
BetabooleanNo

Whether it is a Beta release.

  • true: Yes
  • false: No
true
AcceptLanguagestringNo

Language type of the returned information:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

Data structure.

Messagestring

Message.

success
RequestIdstring

Request ID.

B4EAB48C-BB4B-5B8D-B33B-35D69606C5AD
Configurationobject

Configuration information.

Typestring

Format of the configuration content.

text
AppNamestring

Application name.

test
Tagsstring

Tags of the configuration.

context
Md5string

Message digest of the configuration.

123rfsdf3
DataIdstring

Configuration ID.

log.yaml
Contentstring

Configuration content.

log.level=error
Groupstring

Configuration group name.

test
Descstring

Configuration description.

For testing
EncryptedDataKeystring

Encrypted key.

key
BetaIpsstring

List of IPs for Beta release.

1.1.XX.XX,2.2.XX.XX
GrayVersionsarray<object>

Current gray version information

grayVersionsobject
Typestring

Gray type

Beta
Namestring

Gray version name

test
Rulestring

Rules of the current gray version

a=b
Priorityinteger

The priority of the current gray rule.

20
ErrorCodestring

Error code.

mse-100-000
Successboolean

The result of the request, with values as follows:

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

Examples

Sample success responses

JSONformat

{
  "Message": "success",
  "RequestId": "B4EAB48C-BB4B-5B8D-B33B-35D69606C5AD",
  "Configuration": {
    "Type": "text",
    "AppName": "test",
    "Tags": "context",
    "Md5": "123rfsdf3",
    "DataId": "log.yaml",
    "Content": "log.level=error",
    "Group": "test",
    "Desc": "For testing\n",
    "EncryptedDataKey": "key",
    "BetaIps": "1.1.XX.XX,2.2.XX.XX",
    "GrayVersions": [
      {
        "Type": "Beta",
        "Name": "test",
        "Rule": "a=b",
        "Priority": 20
      }
    ]
  },
  "ErrorCode": "mse-100-000",
  "Success": true
}

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-11-06The response structure of the API has changedView Change Details
2023-04-25API Description UpdateView Change Details