Trigger
Trigger flow based on messages received from a Solace broker.
type: "io.kestra.plugin.solace.Trigger"Trigger flow based on messages received from a Solace broker.
id: trigger_from_solace_queue
namespace: company.team
tasks:
- id: hello
type: io.kestra.plugin.core.log.Log
message: Hello there! I received {{ trigger.messagesCount }} from Solace!
triggers:
- id: read_from_solace
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
The Solace hostname to connect with.
The Deserializer to be used for deserializing messages.
The name of the solace queue to consume from.
The type of the queue to be consumed.
The Solace VPN to connect with.
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.
The maximum time to wait for receiving a number of messages up to maxMessages.
The config properties to be passed to the Deserializer.
Configs in key/value pairs.
The message selector to be used for receiving messages.
Enables support for message selection based on message header parameter and message properties values.
The Solace password.
The Solace properties to be used for connecting to the broker.
List of execution states after which a trigger should be stopped (a.k.a. disabled).
The Solace username.
Number of messages consumed from the Solace broker.
URI of a Kestra's internal storage file containing the messages.