NSQ, A Broker And Its Directory, Messages Counted

NSQ (SHA-256 pinned): nsqd and nsqlookupd as two hardened services from one release on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test publishes four messages, sees the topic count them with the channel holding the last, and asks the directory which broker holds the topic. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticMessaging & Streamingv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

Apache Kafka, One KRaft Node Proven By A Round Trip Gotify, A Push Server Proven By A Message Mail Submission Ports That Refuse Plaintext Mosquitto That Asks Who You Are NATS CLI, A Context Saved And A Check That Says CRITICAL NATS Server On Loopback, JetStream On, Round-Tripped Postfix That Only Sends, And Only Encrypted kafka_exporter, A Real KRaft Broker And An Offset That Moved

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_nsq" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-nsq/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.