A trigger is created.
Debugging
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:
- The required resource types are displayed in bold characters.
- 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 |
---|---|---|---|---|
fc:CreateTrigger | create |
|
| none |
Request syntax
POST /2021-04-06/services/{serviceName}/functions/{functionName}/triggers HTTP/1.1
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
serviceName | string | Yes | The name of the service. | demoService |
functionName | string | Yes | The name of the function. | demoFunction |
body | object | No | The definition of the trigger. | |
invocationRole | string | No | The RAM role that is used by the event source such as Object Storage Service (OSS) to invoke the function. For more information, see Overview . | acs:ram::1234567890:role/fc-test |
qualifier | string | No | The version or alias of the service. | LATEST |
sourceArn | string | No | The Alibaba Cloud Resource Name (ARN) of the trigger event source. This parameter is optional for time triggers, HTTP triggers, and EventBridge-based triggers. This parameter is required for other types of triggers. | acs:oss:cn-shanghai:12345:mybucket |
triggerConfig | string | Yes | The configurations of the trigger. The configurations vary based on the trigger type. For more information about the format, see the following topics:
| {"events": ["oss:ObjectCreated:*"], "filter": {"key": {"prefix": "/prefix", "suffix": ".zip"}}} |
triggerName | string | Yes | The name of the trigger. The name contains only letters, digits, hyphens (-), and underscores (_). The name must be 1 to 128 characters in length and cannot start with a digit or a hyphen (-). | oss_create_object_demo |
triggerType | string | Yes | The type of the trigger. Valid values:
| oss |
description | string | No | The description of the trigger. | trigger for test |
X-Fc-Account-Id | string | No | The ID of your Alibaba Cloud account. | 188077086902**** |
X-Fc-Date | string | No | The time when the request is initiated on the client. The format of the value is: EEE,d MMM yyyy HH:mm:ss GMT. | Wed, 11 May 2022 09:00:00 GMT |
X-Fc-Trace-Id | string | No | The custom request ID. | my-test-trace-id |
Response parameters
Examples
Sample success responses
JSON
format
{
"createdTime": "2016-08-15T15:00:00.000+0000",
"invocationRole": "acs:ram::1234567890:role/fc-test",
"lastModifiedTime": "016-08-15T17:00:00.000+0000",
"qualifier": "LATEST",
"sourceArn": "acs:oss:cn-shanghai:12345:mybucket",
"triggerConfig": "{\"events\": [\"oss:ObjectCreated:*\"], \"filter\": {\"key\": {\"prefix\": \"/prefix\", \"suffix\": \".zip\"}}}",
"triggerName": "oss_create_object_trigger_demo",
"triggerType": "oss",
"description": "trigger for test",
"triggerId": "3e270f2f-cef2-421a-bc86-ff4e8088****",
"domainName": "demo-service-demo-function-jkhksh",
"urlInternet": "https://svc-func-xxxxxxxx.cn-hangzhou.fcapp.run",
"urlIntranet": "https://svc-func-xxxxxxxx.cn-hangzhou-vpc.fcapp.run"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-02-19 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2021-06-30 | The request parameters of the API has changed | View Change Details |
2021-06-30 | The request parameters of the API has changed | View Change Details |
2021-06-30 | The request parameters of the API has changed. The response structure of the API has changed | View Change Details |