0.7.0
0.7.0
This is the first release produced from the team RabbitMQ fork of the plugin.
These release notes do not include a lot of bug fixes and small improvements that happened in the AWeber fork since 0.6.1 before team RabbitMQ decided to fork the project.
General Changes
-
Documentation guide is now embedded into README to simplify maintenance
with multiple concurrently developed branches.GitHub issue: #12.
AWS Backend
-
Support the
AWS_EC2_TAGS
environment variable, its value is supposed to be JSON nowGitHub issue: #7
-
Make it possible to use private instance IP addresses with AWS autoscaling groups
GitHub issue: #14
-
Improve error handling when parsing tags.
GitHub issue: #11.
-
Improve debug logging for AWS API requests
GitHub issue: #15
-
Depend on the team RabbitMQ fork of
rabbitmq-aws
GitHub issue: #8
Consul Backend
-
Re-register with Consul if Consul reports that our node is not known for any reason.
GitHub issue: #2
-
Support deregister_critical_service_after
GitHub issue: #3
-
Support for custom hostnames (e.g. for environments that use DHCP but not dynamic DNS records)
GitHub issue: #4
-
New Consul, Docker Compose and HAproxy example
GitHub issue: #5
-
Support arbitrary strings as Consul node names. Contributed by @ValFadeev.
GitHub issue: #9
-
Allow for clustering with nodes in the warning state if the user opts in. Contributed by @ValFadeev.
GitHub issue: #10