Releases
AMQP / RabbitMQ Module for Ignition 8.3
Every published version of the module, with the Ignition and broker versions it has been verified against, plus a direct download for the .modl asset and the user manual.
v1.0.0
v1.0.0 28 Jul 2026AMQP 0-9-1 / RabbitMQ connectivity for Ignition 8.3: broker connections, Event Stream source and handler, system.amqp scripting, and a MassTransit-compatible preset.
- Ignition:
- 8.3.0+
- Broker:
- RabbitMQ 3.8+ (AMQP 0-9-1)
- Other:
- Event Stream module (optional, for the AMQP source and handler)
Changes
- first release
- licensed module: the EULA ships inside the .modl and is presented on install; fully functional under Ignition's standard trial period, and a purchased licence is activated under Platform > System > Licensing
- broker connections as gateway config resources, listed and health-checked under Connections > Service Connectors
- multi-node host lists, TLS (with optional hostname verification), automatic recovery with exponential backoff
- the broker password is stored as an Ignition secret (Embedded ciphertext or a Referenced secret provider), resolved per connect attempt so a rotated secret needs no restart; the username supports ${ENV_VAR} indirection
- several independent broker connections side by side; a faulted one does not affect the others
- Event Stream source "AMQP Consumer": prefetch-based backpressure, ON_HANDLED / ON_DELIVERY / AUTO ack modes, DEAD_LETTER / REQUEUE / DROP failure handling with bounded redeliveries
- Event Stream handler "AMQP Publisher": publisher confirms, mandatory and persistent flags, {metadata} placeholders in routing keys, static headers, Designer dry run
- MassTransit preset for both source and handler: full envelope, MassTransit's RabbitMQ topology conventions, MT-Fault-* headers on dead-lettered messages
- system.amqp.* scripting namespace: connection info, publish, MassTransit publish/encode/decode, topology declaration, queue inspection. It raises Python exceptions, so a script's `except Exception:` catches a failed call
- Direct endpoint style has an Error Queue, so On Failure = DEAD_LETTER preserves failed messages there rather than discarding them; with no error endpoint configured the discard is now logged, at startup and per message, instead of being silent
- Designer editors for source and handler with hover help on every field and a live topology preview
- user manual (docs/user_manual.md, attached to the release as user_manual.pdf)
Known issues
- No store-and-forward outbox: a publish attempted while the broker is unreachable fails immediately rather than being buffered.
- Static handler headers are not editable in the Designer. Opening and saving a file-provisioned event stream in the Designer drops any headers configured in its config.json.
- Confirm Mode PER_BATCH and PER_MESSAGE currently behave identically: every message is confirmed individually.
- The Designer editors have no interaction test; registration, JSON round-trip and layout are covered, but nothing drives the UI.
- A config edit made immediately after another can be missed by a single configuration scan (an Ignition platform behaviour, and silent). Re-scan until the gateway's view agrees.