Updates information about a trigger, such as the input data source, data processing settings, and tags.
Operation description
- You can update only a trigger that is in the Ready or Failed state. The update operation does not change the trigger status.
- After you update a trigger, the uncompleted tasks under the original trigger are no longer executed. You can call the ResumeTrigger operation to resume the execution of the trigger.
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 Resourcesis 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 |
|---|---|---|---|---|
| imm:UpdateTrigger | update | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| ProjectName | string | Yes | The name of the project. You can obtain the name of the project from the response of the CreateProject operation. | test-project |
| Id | string | Yes | The ID of the trigger. You can obtain the ID of the trigger from the response of the CreateTrigger operation. | trigger-9f72636a-0f0c-4baf-ae78-38b27b****** |
| Input | Input | No | The input data source. | |
| Actions | array<object> | No | The processing templates. | |
| object | No | The processing template. | ||
| Name | string | No | The template name. | doc/convert |
| Parameters | array | No | The template parameters. | |
| string | No | The template parameter. | pages=3 | |
| Tags | object | No | The custom tags. You can search for or filter asynchronous tasks by custom tag. | {"test": "val1"} |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "5A022F78-B9A8-4ACC-BB6B-B35975******"
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2023-07-05 | The request parameters of the API has changed | View Change Details |