1.3.1 (May 22, 2020)
To see the full changelog please use the following link.
A component designed to talk to Advanced Message Queuing Protocol, (AMQP) APIs. AMQP is an open standard for passing business messages between applications or organisations (see amqp.org for more).
AMQP component establishes an asynchronous communications with queues and topics to publish or consume records.
The consumer will register a non-exclusive non-durable queue with
without any dead-letter. Name of the queue will be dynamically generated based on
FLOW_ID prefixed with
queue will be bound to the exchange with specified bound key or multiple bound
keys that are specified in one string separated by commas.
This component will automatically encrypt data that is sent to the queue when following environment variables are set:
ELASTICIO_MESSAGE_CRYPTO_IV- vector for symmetric encryption
ELASTICIO_MESSAGE_CRYPTO_PASSWORD- password for symmetric encryption
These variables are by default available in the platform environment.
Data will be encrypted using symmetric
This component expects user to provide a AMQP URL, username and password should
be embedded as part of the URL, for example
amqp://foo:bar@server. You can
also use URL syntax to provide further parameters and any other options
vHost or port).
Will consume the incoming message object that contains
body with the payload.
If the exchange doesn’t exist it will be created on start.
Optionally you can use
* to wildcard. For more information check the
tutorial provided at the RabbitMQ site.
Will publish the messages into an exchange. This exchange will be created on start if it doesn’t exists.
Following limitations of the component are known:
topicexchanges by default. However, with the
topicexchanges one can emulate