Colin Sullivan

Feature Request: Deployment tools for NATS

1

Ease of install of clusters and NATS components (NATS server, NATS streaming server, Prometheus exporter, etc.). E.g. through Chef, Ansible, Puppet, and others. Ansible is most requested so far.

While most code is tested between tests here and the Redis Connector, reported coverage needs to improve with additional specific unit tests.

This method needs to timeout when the location is unreachable or remote server has stalled.

Implement a plugin with the RabbitMQ java API. https://www.rabbitmq.com/api-guide.html

Shutdown and reload need to be handled cleaner. - Use the Drain() API anytime a NATS connection is closed. - Reject incoming MQ series messages while shutting down or reloading.

Allow support for an include directive similar to what the NATS server does. An example can be found [here]( https://github.com/nats-io/nats-server/blob/e155332e69caa1455e74553c15b121d0c176d69b/conf/includes/users.conf#L3).

Add support to log to a file or syslog.

Option to apply a JetStream update to every asset in an account

1

It'd be great to be able to apply things like replication factor, tags, etc, across the board to every stream in an account (or maybe a subset via regex?). Perhaps...

It'd be good to have documentation for the following NATS Server MQTT parameters: - stream_replicas - consumer_memory_storage - consumer_inactive_threshold Note, `consumer_replicas` is left out because that doesn't seem to be...