Trigger

yaml

type: "io.kestra.plugin.solace.Trigger"

Trigger flow based on messages received from a Solace broker.

Examples

Trigger flow based on messages received from a Solace broker.

yaml

id: TriggerFromSolaceQueue
namespace: company.team
tasks:
  - id: hello
    type: io.kestra.core.tasks.log.Log
    message: Hello there! I received {{trigger.messagesCount}} from Solace!
triggers:
  - id: readFromSolace
    type: "io.kestra.plugin.solace.Trigger"
    interval: PT30S
    host: localhost:55555
    username: admin
    password: admin
    vpn: default
    messageDeserializer: JSON
    queueName: test_queue
    queueType: DURABLE_EXCLUSIVE

Properties

`host`

Type: string
Dynamic: ✔️
Required: ✔️

The Solace hostname to connect with.

`messageDeserializer`

Type: string
Dynamic: ❌
Required: ✔️
Default: STRING
Possible Values:
- STRING
- BINARY
- ION
- JSON

The Deserializer to be used for deserializing messages.

`queueName`

Type: string
Dynamic: ✔️
Required: ✔️

The name of the solace queue to consume from.

`queueType`

Type: string
Dynamic: ❌
Required: ✔️
Possible Values:
- DURABLE_EXCLUSIVE
- DURABLE_NON_EXCLUSIVE
- NON_DURABLE_EXCLUSIVE

The type of the queue to be consumed.

`vpn`

Type: string
Dynamic: ✔️
Required: ✔️
Default: default

The Solace VPN to connect with.

`conditions`

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

List of conditions in order to limit the flow trigger.

`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.