GetRoutineStagingCodeUploadInfo - Edge Security Acceleration

Obtains the release information about the routine code that is released to the staging environment. This information can be used to upload the test code to Object Storage Service (OSS).

Operation description

Every time the code of a routine is released to the staging environment, a version number is generated. Such code is for tests only.
A routine can retain a maximum of 10 code versions. If the number of versions reaches the limit, you must call the DeleteRoutineCodeRevision operation to delete unwanted versions.

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

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.

Operation	Access level	Resource type	Condition key	Associated operation
esa:GetRoutineStagingCodeUploadInfo	none	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
Name	string	No	The routine name.	GetRoutineStagingCodeUploadInfo
CodeDescription	string	No	The code description.	the description of code

Response parameters

Parameter	Type	Description	Example
	object	The response parameters.
RequestId	string	The request ID.	EDBD3EB3-97DA-5465-AEF5-8DCA5DC5E395
CodeVersion	string	The code version.	1710120201067203242
OssPostConfig	object	The configuration information that can be used to upload to OSS.	{ "Url": "http://oss_fake_bucket_url", "OSSAccessKeyId": "xxx", "key": "site_er_js/hello.1418586423220543.unstable.js", "callback": "xxx==", "x:codeDescription": "xxx=", "policy": "xxx", "Signature": "xxx=" }

Examples

Sample success responses

JSONformat

{
  "RequestId": "EDBD3EB3-97DA-5465-AEF5-8DCA5DC5E395",
  "CodeVersion": 1710120201067203300,
  "OssPostConfig": {
    "Url": "http://oss_fake_bucket_url",
    "OSSAccessKeyId": "xxx",
    "key": "site_er_js/hello.1418586423220543.unstable.js",
    "callback": "xxx==",
    "x:codeDescription": "xxx=",
    "policy": "xxx",
    "Signature": "xxx="
  }
}

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	InvalidParameter	The specified parameter is invalid.	The specified parameter is invalid.
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	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	CodeVersionNumberExceedQuotaLimit	The maximum number of code versions in your plan has been reached. Check your plan quota and upgrade the plan to request a quota increase.	The maximum number of code versions in your plan has been reached. Check your plan quota and upgrade the plan to request a quota increase.
400	RoutineUserServiceStatusHalt	Failed to update the configurations because you have overdue payments.	Failed to update the configurations because you have overdue payments.

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

Change history

Change time	Summary of changes	Operation
2024-12-04	The Error code has changed	View Change Details