PublishRoutineCodeVersion - Edge Security Acceleration - Alibaba Cloud Documentation Center

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

esa:PublishRoutineCodeVersion

none

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
Name	string	Yes	The name of the Edge Routine.	test-routine1
Env	string	Yes	The environment name.	production
CodeVersion	string	No	The version number of the code to publish.	1710120201067203242

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	EDBD3EB3-97DA-5465-AEF5-8DCA5DC5E395
CodeVersion	string	The code version number.	1710120201067203242

Examples

Success response

JSON format

{
  "RequestId": "EDBD3EB3-97DA-5465-AEF5-8DCA5DC5E395",
  "CodeVersion": "1710120201067203242"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InternalException	Failed to call the service. Try again later or contact technical support.	Failed to call the service. Try again later or contact technical support.
400	RoutineNotExist	The routine name does not exist. Check the routine name and try again.	The routine name does not exist. Check the routine name and try again.
400	ParameterNotExist	The specified parameter does not exist. Check your configurations and try again.	The specified parameter does not exist. Check your configurations and try again.
400	InternalOperationError	Failed to call the service. Try again later or contact technical support.	Failed to call the service. Try again later or contact technical support.
400	DependedByOthers	Failed to call the service. Try again later or contact technical support.	Failed to call the service. Try again later or contact technical support.
400	RoutineUserServiceStatusHalt	Failed to update the configurations because you have overdue payments.	Failed to update the configurations because you have overdue payments.
400	InvalidParameter	Parameter verification failed. Check your configurations and try again.	Parameter verification failed. Check your configurations and try again.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.