Version History¶

`2.1.1`_ May 3, 2017¶

Fix intentional closing of an AMQP connection
New behavior for publishing that raises exception
Add publisher confirmations
Make sprockets.mixins.amqp.install() work with sprockets.http
Add support for environment variables prefixed with AMQP_ or RABBITMQ
Clean up AMQP message property behavior, make defaults, but don’t change already set values
Automatically create the default app_id AMQP message property
Split out tests into a mix of unit tests and integration tests
Update state behaviors, names, and transitions
All publishing is mandatory, returned messages are logged, a callback can be registered

Move Mixin and AMQP client to separate files
Replace AMQP connection handling code with latest internal version
Provide ability to register callbacks for ready, unavailable, and persistent failure states
Remove default AMQP URL from AMQP class, url is now a required parameter for install
Rename amqp_publish ‘message’ parameter to ‘body’
Add properties for all AMQP states
Provide mandatory AMQP properties (app_id, correlation_id, message_id, timestamp) automatically
- Mandatory properties cannot be overridden
Add unit test coverage for new functionality
- Test execution requires a running AMQP server

Connect to AMQP in sprockets.mixins.amqp.install and maintain and persist connection
Change to use tornado locks.Condition vs locks.Event

Initial implementation