CreateRoutineCodeDeployment - Edge Security Acceleration

Release the version of the function code in proportion to the specified environment.

Operation description

Request description

When you create a version for deployment, you can set the environment name Env parameter only to the test environment staging or the production environment production.
CodeVersions parameter supports up to two versions of a phased release, and the sum of the proportions of these versions must be equal to 100%.

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.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
Name	string	Yes	The function name.	test
Env	string	Yes	The name of the environment. Only supports test environment `staging` or production environment `production`.	staging
Strategy	string	Yes	The deployment policy. Valid value: percentage.	percentage
CodeVersions	array<object>	Yes	The configuration list of phased release version numbers. A maximum of two versions are supported, and the sum of the total proportions is equal to 100.
	object	Yes	Phased release version number.
Percentage	long	Yes	The phased release ratio of the code version. Valid values: 1 to 100.	100
CodeVersion	string	Yes	The version of the code.	1723599747213377175

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	EDBD3EB3-97DA-5465-AEF5-8DCA5DC5E395
Strategy	string	The phased release policy. The constant string is "percentage".	percentage
DeploymentId	string	The deployment record ID.	234
CodeVersions	array<object>	The configuration list of the phased release version number.
Versions	object	The configuration of the phased release version number.
Percentage	long	The phased release ratio.	100
CodeVersion	string	The version of the code.	1723599747213377175

Examples

Sample success responses

JSONformat

{
  "RequestId": "EDBD3EB3-97DA-5465-AEF5-8DCA5DC5E395",
  "Strategy": "percentage",
  "DeploymentId": 234,
  "CodeVersions": [
    {
      "Percentage": 100,
      "CodeVersion": 1723599747213377300
    }
  ]
}

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.

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

Change history

Change time	Summary of changes	Operation
2025-12-11	API Description Update. The Error code has changed	View Change Details