All Products
Search
Document Center

ENS:PushApplicationData

Last Updated:Oct 09, 2026

Pre-pushes the business or service data of an application to a file server.

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

ens:PushApplicationData

update

*All Resource

*

None None

Request parameters

Parameter

Type

Required

Description

Example

Data

string

Yes

The list of data files to be pre-pushed, in the string format of a JSON array.

[{\"name\":\"app01\", \"version\":\"1.0\", \"size\":100,\"archiveType\":\"tar.gz\", \"md5\":\"\", \"url\":\"http://xxxx\",\"timeout\": 1000 }, { \"name\":\"app02\", \"version\":\"1.1\", \"size\":10,\"archiveType\":\"zip\", \"md5\":\"xxxx\", \"url\":\"http://xxxxxx\",\"timeout\": 1000 }]

AppId

string

Yes

The application ID.

Before calling this operation, activate the Edge Application Hosting service and create an application by calling CreateApplication. Obtain the AppId from the response of the CreateApplication operation.

e76f8985-7965-41fc-925b-9648bb6bf650

Timeout

integer

No

This parameter is invalid.

1800

PushStrategy

string

No

The canary pre-push policy in JSON string format. Multiple distribution policies are supported. By default, all data is pre-pushed.

{\"name\": \"ScheduleToRegionId\", \"parameters\":{ \"operator\": \"In\", \"values\": [\"cn-chegndu-telecom-4\", \"cn-shanghai-cmcc-4\"] }}

Response elements

Element

Type

Description

Example

object

PushResults

object

PushResult

array<object>

The execution results of the pre-push operations for each data file.

object

The execution result of the pre-push operation for a data file.

Name

string

The name of the data file.

gcs-pre-websocket-eip-telecom

ResultCode

integer

The pre-push error code. Valid values:

  • 0: The pre-push operation succeeded.

  • 100: The pre-push operation was already executed, and the current pre-push status is Pre-push Successful.

  • 200: The pre-push operation was already executed, and the current pre-push status is Pre-pushing (some file servers are in the pre-pushing state).

  • 300: The pre-push operation failed and must be triggered again. For the specific error description, refer to ResultDescrip.

100

ResultDescrip

string

The description of the status result.

Success

Version

string

The version number of the data file.

standard

RequestId

string

The request ID.

473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E

Examples

Success response

JSON format

{
  "PushResults": {
    "PushResult": [
      {
        "Name": "gcs-pre-websocket-eip-telecom",
        "ResultCode": 100,
        "ResultDescrip": "Succeeded",
        "Version": "standard"
      }
    ]
  },
  "RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E"
}

Error codes

HTTP status code

Error code

Error message

Description

400 NoPermission Permission denied.
400 InvalidParameter.%s The specified field %s invalid. Please check it again.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.