Trigger

yaml

type: "io.kestra.plugin.redis.list.Trigger"

Removes and returns an element from the head of a list periodically and create one execution per batch.

If you would like to consume each message from a list in real-time and create one execution per message, you can use the io.kestra.plugin.redis.list.RealtimeTrigger instead.

Examples

yaml

id: list_listen
namespace: company.team

tasks:
  - id: echo
    type: io.kestra.plugin.core.log.Log
    message: "{{ trigger.uri }} containing {{ trigger.count }} lines"

triggers:
  - id: watch
    type: io.kestra.plugin.redis.list.Trigger
    url: redis://localhost:6379/0
    key: mytriggerkey
    maxRecords: 2

Properties

`key`

Type: string
Dynamic: ✔️
Required: ✔️

The redis key for the list.

`serdeType`

Type: object
Dynamic: ❓
Required: ✔️

`url`

Type: string
Dynamic: ✔️
Required: ✔️

The connection string.

`conditions`

Type: array
SubType: Condition
Dynamic: ❌
Required: ❌

List of conditions in order to limit the flow trigger.

`count`

Type:
- integer
- string
Dynamic: ✔️
Required: ❌

`interval`

Type: string
Dynamic: ❌
Required: ❌
Default: 60.000000000
Format: duration

Interval between polling.

The interval between 2 different polls of schedule, this can avoid to overload the remote system with too many calls. For most of the triggers that depend on external systems, a minimal interval must be at least PT30S. See ISO_8601 Durations for more information of available interval values.