Update plugin configurations with the UpdatePluginConfig API - Microservices Engine - Alibaba Cloud - Microservices Engine

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

mse:UpdatePluginConfig

update

*Gateway

acs:mse:{#regionId}:{#accountId}:instance/{#GatewayUniqueId}

None

Request parameters

Parameter	Type	Required	Description	Example
Id	integer	No		1
GatewayId `deprecated`	integer	No		1
GatewayUniqueId	string	No		gw-ubuwqygbq4783gqb2y3f87q****
PluginId	integer	No		2
Enable	boolean	No		true
Config	string	No
ConfigLevel	integer	Yes		0
ResourceIdList	array	No
	integer	No		200
GmtCreate `deprecated`	string	No		1667309705000
GmtModified `deprecated`	string	No		1667309705000
AcceptLanguage	string	No		zh

Response elements

Parameter	Type	Description	Example
	object	RestResult
RequestId	string		03A3E2F4-6804-5663-9D5D-2EC47A1*****
Success	boolean		true
Code	integer		200
ErrorCode	string		500
HttpStatusCode	integer		200
Message	string		success
DynamicMessage	string		code
Data	integer		1

Examples

Success response

format

{
  "RequestId": "03A3E2F4-6804-5663-9D5D-2EC47A1*****",
  "Success": true,
  "Code": 200,
  "ErrorCode": "500",
  "HttpStatusCode": 200,
  "Message": "success",
  "DynamicMessage": "code",
  "Data": 1
}

Error codes

HTTP status code	Error code	Error message
400	IllegalRequest	Invalid request:%s
400	InvalidParameter	Parameter error:%s
500	InternalError	Console error. Try again later:%s
403	NoPermission	You are not authorized to perform this operation:%s
404	NotFound	Not found:%s

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.