Adds a Nacos service source.
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:
- 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.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
mse:AddServiceSource | create |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Type | string | No | The type of the service source.
| The Ingress configuration. |
Source | string | Yes | The service source.
| K8s,MSE |
Address | string | No | Specifies whether to monitor Ingress classes. | c9ad2a0717032427e920754e25b49e3b5 |
Name | string | Yes | The namespace whose resources you want to monitor. | istio |
GatewayUniqueId | string | Yes | Specifies whether to update the Ingress status. | gw-c70622ff52fe49beb29bea9a6f52**** |
IngressOptionsRequest | object | No | The list of service groups. | |
EnableIngress | boolean | No | The group to which the service belongs. | true |
IngressClass | string | No | An array of service root paths. | com.test.xxx |
WatchNamespace | string | No | The root path of the service. | default |
EnableStatus | boolean | No | The language of the response. Valid values:
| true |
ToAuthorizeSecurityGroups | array<object> | No | The list of security groups to be authorized. You can specify security groups to allow backend services to access data sources that you create. | |
ToAuthorizedSecurityGroup | object | No | ||
SecurityGroupId | string | No | The ID of the security group. | sg-bp1acepclex0vmi1**** |
PortRange | string | No | The authorized port range of the security group. You can select multiple port ranges. Separate each port range with a comma (,). | 8080/8080,9000/10000 |
Description | string | No | The description of the authorization record. | rule for xxx |
GroupList | array | No | The data structure. | |
string | No | The ID of the request. | NACOS | |
PathList | array | No | The HTTP status code returned. | |
string | No | The message returned. | /test | |
AcceptLanguage | string | No | The language of the response. Valid values:
| zh-CN |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "D0DB055C-51F2-5BB2-82A6-CD8A3C6EE6BA",
"HttpStatusCode": 200,
"Message": "You are not authorized to perform this operation. Action: mse:AddServiceSource, Resource: acs:mse:cn-hangzhou:1105471854403716:instance/gw-082c943a8c304e48a37a7a29a5ddeda7",
"Code": 200,
"Success": true,
"Data": 63
}
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 |
---|---|---|
2023-12-11 | The request parameters of the API has changed | View Change Details |
2022-08-09 | The request parameters of the API has changed | View Change Details |