hutch 0.24.0 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: fb197fc767359bc60d35790ec650c9c077120d0d
-  data.tar.gz: e1152a8d434fdc9a4752c095ad5fdce4871ffd9e
+SHA256:
+  metadata.gz: 626b85f02b69ee2113376ff382173fd124cdcae1bdc404f0681874e76a80310e
+  data.tar.gz: 3d1d6a2cd275b1c2d72d4842841ad90f70145cabe6800ff3860b206aebf0308e
 SHA512:
-  metadata.gz: c34020a830413a6e970bfae9e59fecdaebbe770aaf7df753a7f263af6d7dc98b0ae4433a4aafc27d9d8f45689168d0b39a64d3ba4086c05187fc7b0e352d9814
-  data.tar.gz: cc24d3e6ab11c4979455c06ba057760b00cffae9dd577a39f4f89bfe7b45a33378c2190362c2d003a5418b3e64238d2997610c8b4f8f52a5287d0765563109ad
+  metadata.gz: c1b0c80bf6362b0cfbc6f54b3257c74549c6d927fbae3bcaecb50aeb4ed0f28e01466a6a3013ce9175f55eb481b2e9378f89954edcc1453753da00b76873c766
+  data.tar.gz: 4c346421c5c1fa49440866b56486cc75d68c3eed8c3014ae2f51e2643f40a59b084634248b52d32965b65f692d1560250a8f5add30c4b75b2f541c895574aa26

data/.travis.yml

@@ -1,19 +1,24 @@
+dist: bionic
+sudo: required
+
 language: ruby
 cache: bundler
 before_install:
-  - gem update --system
   - gem install bundler
+before_script:
+  - "./bin/ci/install_on_debian.sh"
+  - until sudo lsof -i:5672; do echo "Waiting for RabbitMQ to start..."; sleep 1; done
+  - "./bin/ci/before_build.sh"
 matrix:
   include:
-    - rvm: 2.4.0
-    - rvm: 2.3.3
-    - rvm: 2.2
-    - rvm: 2.1
-    - rvm: 2.0
-    - rvm: jruby-9.1.7.0
-      jdk: oraclejdk8
-      env:
-        - JRUBY_OPTS='--debug'
-
-services:
-  - rabbitmq
+    - rvm: "2.7.1"
+    - rvm: "2.6.6"
+    - rvm: "2.5.8"
+    - rvm: "2.4.10"
+    - rvm: "2.3.8"
+    - rvm: "jruby-9.2.9.0"
+    - rvm: "ruby-head"
+  allow_failures:
+    rvm:
+      - "jruby-9.2.9.0"
+      - ruby-head

data/CHANGELOG.md

@@ -1,4 +1,228 @@
-## 0.24.0 — (unreleased)
+## 1.0.1 (in development)
+
+No changes yet.
+
+## 1.0.0 (April 8th, 2020)
+
+Hutch has been around for several years. It is time to ship a 1.0. With it we try to correct
+a few of overly opinionated decisions from recent releases. This means this release
+contains potentially breaking changes.
+
+### Breaking Changes
+
+ * Hutch will no longer configure any queue type (such as [quorum queues](https://www.rabbitmq.com/quorum-queues.html))
+   or queue mode (used by classic [lazy queues](https://www.rabbitmq.com/lazy-queues.html))
+   by default as that can be breaking change for existing Hutch and RabbitMQ installations due to the
+   [property equivalence requirement](https://www.rabbitmq.com/queues.html#property-equivalence) in AMQP 0-9-1.
+
+   This means **some defaults introduced in `0.28.0` ([gocardless/hutch#341](https://github.com/gocardless/hutch/pull/341)) were reverted**.
+   The user has to opt in to configure the queue type and mode and other [optional arguments](https://www.rabbitmq.com/queues.html#optional-arguments) they need to use.
+   Most optional arguments can be set via [policies](https://www.rabbitmq.com/parameters.html#policies) which is always the recommended approach. 
+   Queue type, unfortunately, is not one of them as different queue types have completely different
+   implementation details, on disk data formats and so on.
+
+   To use a quorum queue, use the `quorum_queue` consumer DSL method:
+
+   ``` ruby
+   class ConsumerUsingQuorumQueue
+      include Hutch::Consumer
+      consume 'hutch.test1'
+      # when in doubt, prefer using a policy to this DSL
+      # https://www.rabbitmq.com/parameters.html#policies
+      arguments 'x-key': :value
+        
+      quorum_queue
+   end
+   ```
+
+   To use a classic lazy queue, use the `lazy_queue` consumer DSL method:
+
+   ``` ruby
+   class ConsumerUsingLazyQueue
+     include Hutch::Consumer
+     consume 'hutch.test1'
+     # when in doubt, prefer using a policy to this DSL
+      # https://www.rabbitmq.com/parameters.html#policies
+      arguments 'x-key': :value
+     
+     lazy_queue
+     classic_queue
+   end
+   ```
+
+   By default Hutch will not configure any `x-queue-type` or `x-queue-mode` optional arguments
+   which is identical to RabbitMQ defaults (a regular classic queue).
+
+   Note that as of RabbitMQ 3.8.2, an omitted `x-queue-type` is [considered to be identical](https://github.com/rabbitmq/rabbitmq-common/issues/341)
+   to `x-queue-type` set to `classic` by RabbitMQ server.
+
+
+   #### Enhancements
+
+    * Exchange type is now configurable via the `` config setting. Supported exchanges must be
+      compatible with topic exchanges (e.g. wrap it). Default value is `"topic"`.
+
+      This feature is limited to topic and delayed message exchange plugins and is mostly
+      useful for forward compatibility.
+
+      Contributed by Michael Bumann.
+
+      GitHub issue: [gocardless/hutch#349](https://github.com/gocardless/hutch/pull/349)
+
+
+## 0.28.0 (March 17, 2020)
+
+### Enhancements
+
+  * Add lazy and quorum options for queues.
+
+    GitHub issue: [gocardless/hutch#341](https://github.com/gocardless/hutch/pull/341)
+
+    Contributed by: Arthur Del Esposte
+
+  * Log level in the message publisher switched to DEBUG.
+
+    GitHub issue: [gocardless/hutch#343](https://github.com/gocardless/hutch/pull/343)
+
+    Contributed by: Codruț Constantin Gușoi
+
+### Documentation
+
+  * Add zeitwerk note to README.
+
+    GitHub issue: [gocardless/hutch#342](https://github.com/gocardless/hutch/pull/342)
+
+    Contributed by: Paolo Zaccagnini
+
+### CI
+
+  * Use jruby-9.2.9.0
+
+    GitHub issue: [gocardless/hutch#336](https://github.com/gocardless/hutch/pull/336)
+
+    Contributed by: Olle Jonsson
+
+## 0.27.0 (September 9th, 2019)
+
+### Enhancements
+
+ * Error handler for Rollback.
+
+   GitHub issue: [gocardless/hutch#332](https://github.com/gocardless/hutch/pull/332)
+
+   Contributed by Johan Kok.
+
+### Bug Fixes
+
+ * Allow for the latest ActiveSupport version.
+
+   GitHub issue: [gocardless/hutch#334](https://github.com/gocardless/hutch/pull/334)
+
+ * Signal tests are now skipped on JRuby.
+
+   Contributed by Olle Jonsson.
+
+   GitHub issue: [gocardless/hutch#326](https://github.com/gocardless/hutch/pull/326)
+
+### Dependency Bumps
+
+Bunny and other dependencies were updated to their latest release
+series.
+
+
+## 0.26.0 (February 13th, 2019)
+
+### Dependency Bumps
+
+Bunny and other dependencies were updated to their latest release
+series.
+
+### Synchronized Connection Code
+
+The methods that connect to RabbitMQ are now synchronized which makes
+them safer to use in concurrent settings. Note that Hutch still
+uses a single Bunny channel which is not meant to be shared
+between threads without application-level synchronization for publishing.
+
+Contributed by Chris Barton.
+
+GitHub issue: [#308](https://github.com/gocardless/hutch/pull/308).
+
+### More Bunny Options Propagated
+
+Contributed by Damian Le Nouaille.
+
+GitHub issue: [#322](https://github.com/gocardless/hutch/pull/322).
+
+### Removed Opbeat Integration
+
+The service is no longer generally available.
+
+Contributed by Olle Jonsson.
+
+GitHub issue: [#313](https://github.com/gocardless/hutch/pull/313)
+
+
+## 0.25.0 - January 17th, 2018
+
+### Consumer groups
+
+Consumer groups allow you to run groups of consumers together, rather than running them
+all at once in a single process. You define groups in your config file, and then specify
+a `--only-group` option when starting up Hutch with `hutch`.
+
+Contributed by Nickolai Smirnov.
+
+GitHub pull request: [#296](https://github.com/gocardless/hutch/pull/296)
+
+### Fix configuring Hutch with a URI
+
+When Hutch is configured to connect to RabbitMQ with a URI, we should respect the
+`amqps` specification, defaulting to the standard protocol ports when not specified.
+
+This means, for example, that `amqp://guest:guest@127.0.0.1/` connects to the server on
+port 5672 and does not use TLS, whereas `amqps://guest:guest@127.0.0.1/` connects to the
+server on port 5671 and uses TLS.
+
+This behaviour was introduced in [#159](https://github.com/gocardless/hutch/pull/159) but
+broken since then. This fixes it, and includes tests.
+
+Contributed by Michael Canden-Lennox.
+
+GitHub pull request: [#305](https://github.com/gocardless/hutch/pull/305)
+
+### Pass exceptions when setting up the client to configured error handlers
+
+When an error occurs during Hutch's startup, it is currently not passed to the configured
+error handlers. This starts handling those exceptions.
+
+Contributed by Valentin Krasontovitsch.
+
+GitHub issue: [#288](https://github.com/gocardless/hutch/issues/288)
+GitHub pull request: [#301](https://github.com/gocardless/hutch/pull/301)
+
+### Log the Rails environment when running Hutch in verbose mode
+
+When starting up Hutch in verbose mode with `hutch -v`, the Rails environment is now
+logged.
+
+Contributed by [@wppurking](https://github.com/wppurking).
+
+GitHub pull request: [#282](https://github.com/gocardless/hutch/pull/282)
+
+### Make the Honeybadger error handler compatible with new versions of `honeybadger-ruby`
+
+[`honeybadger-ruby`](https://github.com/honeybadger-io/honeybadger-ruby/)
+[changed](https://github.com/honeybadger-io/honeybadger-ruby/blob/master/CHANGELOG.md#300---2017-02-06)
+its API in v3.0.0. This updates our error handler to work with that, whilst still
+maintaining our existing behaviour.
+
+Contributed by Olle Jonsson and Bill Ruddock.
+
+GitHub pull requests: [#274](https://github.com/gocardless/hutch/pull/274),
+[#290](https://github.com/gocardless/hutch/pull/290)
+
+## 0.24.0 — February 1st, 2017
 
 ### Configurable Consumer Prefixes
 
@@ -14,7 +238,7 @@ Hutch will now handle several OS signals:
 
  * `USR2` will log stack traces of all alive VM threads
  * `QUIT` (except on JRuby), `INT`, `TERM` will cause Hutch daemon to shut down
- 
+
  Contributed by Olle Jonsson.
 
 GitHub issues: [#263](https://github.com/gocardless/hutch/pull/263), [#271](https://github.com/gocardless/hutch/pull/271)
@@ -98,7 +322,7 @@ Contributed by Seamus Abshere.
 
 ### Worker: Log received messages using level DEBUG instead of INFO
 
-Received messages used to be logged using severity level INFO. 
+Received messages used to be logged using severity level INFO.
 This has been lowered to DEBUG.
 
 Contributed by Jesper Josefsson.
@@ -630,4 +854,3 @@ Hutch.global_properties = proc {
 ## 0.1.0 - September 9, 2013
 
 - Initial release
-

data/Gemfile

@@ -1,6 +1,6 @@
 source 'https://rubygems.org'
 
-ruby RUBY_VERSION
+ruby '>= 2.3.0'
 
 gemspec
 
@@ -23,8 +23,8 @@ group :development, :test do
   gem "honeybadger"
   gem "coveralls", "~> 0.8.15", require: false
   gem "newrelic_rpm"
-  gem "airbrake", "~> 5.0"
-  gem "opbeat", "~> 3.0.9"
+  gem "airbrake", "~> 10.0"
+  gem "rollbar"
 end
 
 group :development, :darwin do

data/LICENSE

@@ -1,4 +1,5 @@
 Copyright (c) 2013-2016 GoCardless
+Copyright (c) 2016-2020 Hutch contributors
 
 Permission is hereby granted, free of charge, to any person
 obtaining a copy of this software and associated documentation

data/README.md

@@ -2,7 +2,6 @@
 
 [![Gem Version](https://badge.fury.io/rb/hutch.svg)](http://badge.fury.io/rb/hutch)
 [![Build Status](https://travis-ci.org/gocardless/hutch.svg?branch=master)](https://travis-ci.org/gocardless/hutch)
-[![Dependency Status](https://gemnasium.com/gocardless/hutch.svg)](https://gemnasium.com/gocardless/hutch)
 [![Code Climate](https://codeclimate.com/github/gocardless/hutch.svg)](https://codeclimate.com/github/gocardless/hutch)
 
 Hutch is a Ruby library for enabling asynchronous inter-service communication
@@ -40,7 +39,7 @@ gem install hutch
 
 ## Requirements
 
-- Hutch requires Ruby 2.0+ or JRuby 9K.
+- Hutch requires Ruby 2.3+ or JRuby 9K.
 - Hutch requires RabbitMQ 3.3 or later.
 
 ## Overview
@@ -59,8 +58,9 @@ Hutch uses [Bunny](http://rubybunny.info) or [March Hare](http://rubymarchhare.i
 
 ### Project Maturity
 
-Hutch is a moderately mature project (started in early 2013)
-that was extracted from production systems.
+Hutch is a mature project that was originally extracted from production systems
+at [GoCardless](https://gocardless.com) in 2013 and is now maintained by a large
+group of contributors.
 
 ## Consumers
 
@@ -80,8 +80,8 @@ message[:id]  # => "02ABCXYZ"
 To subscribe to a topic, pass a routing key to `consume` in the class
 definition. To bind to multiple routing keys, simply pass extra routing keys
 in as additional arguments. Refer to the [RabbitMQ docs on topic exchanges
-][topic-docs] for more information about how to use routing keys. Here's an
-example consumer:
+](http://www.rabbitmq.com/tutorials/tutorial-five-ruby.html) for more information
+about how to use routing keys. Here's an example consumer:
 
 ```ruby
 class FailedPaymentConsumer
@@ -109,6 +109,28 @@ class FailedPaymentConsumer
 end
 ```
 
+It is possible to set some custom options to consumer's queue explicitly.
+This example sets the consumer's queue as a
+[quorum queue](https://www.rabbitmq.com/quorum-queues.html)
+and to operate in the [lazy mode](https://www.rabbitmq.com/lazy-queues.html).
+The `initial_group_size`
+[argument](https://www.rabbitmq.com/quorum-queues.html#replication-factor) is
+optional.
+
+```ruby
+class FailedPaymentConsumer
+  include Hutch::Consumer
+  consume 'gc.ps.payment.failed'
+  queue_name 'failed_payments'
+  lazy_queue
+  quorum_queue initial_group_size: 3
+
+  def process(message)
+    mark_payment_as_failed(message[:id])
+  end
+end
+```
+
 You can also set custom arguments per consumer. This example declares a consumer with
 a maximum length of 10 messages:
 
@@ -120,7 +142,9 @@ class FailedPaymentConsumer
 end
 ```
 
-Custom queue arguments can be found on [this page](https://www.rabbitmq.com/extensions.html).
+This sets the `x-max-length` header. For more details, see the [RabbitMQ
+documentation on Queue Length Limit](https://www.rabbitmq.com/maxlength.html). To find out more
+about custom queue arguments, consult the [RabbitMQ documentation on AMQP Protocol Extensions](https://www.rabbitmq.com/extensions.html).
 
 Consumers can write to Hutch's log by calling the logger method. The logger method returns
 a [Logger object](http://ruby-doc.org/stdlib-2.1.2/libdoc/logger/rdoc/Logger.html).
@@ -164,7 +188,7 @@ This will enable NewRelic custom instrumentation:
 Hutch::Config.set(:tracer, Hutch::Tracers::NewRelic)
 ```
 
-Batteries included! 
+Batteries included!
 
 ## Running Hutch
 
@@ -217,6 +241,24 @@ directory of a Rails app, or pass the path to a Rails app in with the
 the `app/consumers/` directory, to allow them to be auto-loaded when Rails
 boots.
 
+If you're using the new Zeitwerk autoloader (enabled by default in Rails 6)
+and the consumers are not loaded in development environment you will need to
+trigger the autoloading in an initializer with
+
+```ruby
+::Zeitwerk::Loader.eager_load_all 
+```
+
+or with something more specific like
+
+```ruby
+autoloader = Rails.autoloaders.main
+
+Dir.glob(File.join('app/consumers', '*_consumer.rb')).each do |consumer|
+  autoloader.preload(consumer)
+end
+```
+
 To require files that define consumers manually, simply pass each file as an
 option to `--require`. Hutch will automatically detect whether you've provided
 a Rails app or a standard file, and take the appropriate behaviour:
@@ -300,8 +342,8 @@ AMQP.connect(host: config[:host]) do |connection|
 end
 ```
 
-If using publisher confirms with amqp gem, see [this issue][pc-issue]
-and [this gist][pc-gist] for more info.
+If using publisher confirms with amqp gem, see [this issue](https://github.com/ruby-amqp/amqp/issues/92)
+and [this gist](https://gist.github.com/3042381) for more info.
 
 ## Configuration
 
@@ -339,6 +381,8 @@ Known configuration parameters are:
  * `connection_timeout`: Bunny's socket open timeout (default: `11`)
  * `read_timeout`: Bunny's socket read timeout (default: `11`)
  * `write_timeout`: Bunny's socket write timeout (default: `11`)
+ * `automatically_recover`: Bunny's enable/disable network recovery (default: `true`)
+ * `network_recovery_interval`: Bunny's reconnect interval (default: `1`)
  * `tracer`: tracer to use to track message processing
 
 ### Environment variables
@@ -384,245 +428,201 @@ Generate with
     </tr>
   </thead>
   <tbody>
-  
     <tr>
       <td><tt>mq_host</tt></td>
       <td>127.0.0.1</td>
       <td>String</td>
       <td><tt>HUTCH_MQ_HOST</tt></td>
-      <td><p>RabbitMQ hostname</p>
-</td>
+      <td><p>RabbitMQ hostname</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_exchange</tt></td>
       <td>hutch</td>
       <td>String</td>
       <td><tt>HUTCH_MQ_EXCHANGE</tt></td>
-      <td><p>RabbitMQ Exchange to use for publishing</p>
-</td>
+      <td><p>RabbitMQ Exchange to use for publishing</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_vhost</tt></td>
       <td>/</td>
       <td>String</td>
       <td><tt>HUTCH_MQ_VHOST</tt></td>
-      <td><p>RabbitMQ vhost to use</p>
-</td>
+      <td><p>RabbitMQ vhost to use</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_username</tt></td>
       <td>guest</td>
       <td>String</td>
       <td><tt>HUTCH_MQ_USERNAME</tt></td>
-      <td><p>RabbitMQ username to use.</p>
-</td>
+      <td><p>RabbitMQ username to use.</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_password</tt></td>
       <td>guest</td>
       <td>String</td>
       <td><tt>HUTCH_MQ_PASSWORD</tt></td>
-      <td><p>RabbitMQ password</p>
-</td>
+      <td><p>RabbitMQ password</p></td>
     </tr>
-  
     <tr>
       <td><tt>uri</tt></td>
       <td>nil</td>
       <td>String</td>
       <td><tt>HUTCH_URI</tt></td>
-      <td><p>RabbitMQ URI (takes precedence over MQ username, password, host, port and vhost settings)</p>
-</td>
+      <td><p>RabbitMQ URI (takes precedence over MQ username, password, host, port and vhost settings)</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_api_host</tt></td>
       <td>127.0.0.1</td>
       <td>String</td>
       <td><tt>HUTCH_MQ_API_HOST</tt></td>
-      <td><p>RabbitMQ HTTP API hostname</p>
-</td>
+      <td><p>RabbitMQ HTTP API hostname</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_port</tt></td>
       <td>5672</td>
       <td>Number</td>
       <td><tt>HUTCH_MQ_PORT</tt></td>
-      <td><p>RabbitMQ port</p>
-</td>
+      <td><p>RabbitMQ port</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_api_port</tt></td>
       <td>15672</td>
       <td>Number</td>
       <td><tt>HUTCH_MQ_API_PORT</tt></td>
-      <td><p>RabbitMQ HTTP API port</p>
-</td>
+      <td><p>RabbitMQ HTTP API port</p></td>
     </tr>
-  
     <tr>
       <td><tt>heartbeat</tt></td>
       <td>30</td>
       <td>Number</td>
       <td><tt>HUTCH_HEARTBEAT</tt></td>
-      <td><p><a href="http://rabbitmq.com/heartbeats.html">RabbitMQ heartbeat timeout</a></p>
-</td>
+      <td><p><a href="http://rabbitmq.com/heartbeats.html">RabbitMQ heartbeat timeout</a></p></td>
     </tr>
-  
     <tr>
       <td><tt>channel_prefetch</tt></td>
       <td>0</td>
       <td>Number</td>
       <td><tt>HUTCH_CHANNEL_PREFETCH</tt></td>
-      <td><p>The <tt>basic.qos</tt> prefetch value to use.</p>
-</td>
+      <td><p>The <tt>basic.qos</tt> prefetch value to use.</p></td>
     </tr>
-  
     <tr>
       <td><tt>connection_timeout</tt></td>
       <td>11</td>
       <td>Number</td>
       <td><tt>HUTCH_CONNECTION_TIMEOUT</tt></td>
-      <td><p>Bunny's socket open timeout</p>
-</td>
+      <td><p>Bunny's socket open timeout</p></td>
     </tr>
-  
     <tr>
       <td><tt>read_timeout</tt></td>
       <td>11</td>
       <td>Number</td>
       <td><tt>HUTCH_READ_TIMEOUT</tt></td>
-      <td><p>Bunny's socket read timeout</p>
-</td>
+      <td><p>Bunny's socket read timeout</p></td>
     </tr>
-  
     <tr>
       <td><tt>write_timeout</tt></td>
       <td>11</td>
       <td>Number</td>
       <td><tt>HUTCH_WRITE_TIMEOUT</tt></td>
-      <td><p>Bunny's socket write timeout</p>
-</td>
+      <td><p>Bunny's socket write timeout</p></td>
+    </tr>
+    <tr>
+      <td><tt>automatically_recover</tt></td>
+      <td>true</td>
+      <td>Boolean</td>
+      <td><tt>HUTCH_AUTOMATICALLY_RECOVER</tt></td>
+      <td><p>Bunny's enable/disable network recovery</p></td>
+    </tr>
+    <tr>
+      <td><tt>network_recovery_interval</tt></td>
+      <td>1</td>
+      <td>Number</td>
+      <td><tt>HUTCH_NETWORK_RECOVERY_INTERVAL</tt></td>
+      <td><p>Bunny's reconnect interval</p></td>
     </tr>
-  
     <tr>
       <td><tt>graceful_exit_timeout</tt></td>
       <td>11</td>
       <td>Number</td>
       <td><tt>HUTCH_GRACEFUL_EXIT_TIMEOUT</tt></td>
-      <td><p>FIXME: DOCUMENT THIS</p>
-</td>
+      <td><p>FIXME: DOCUMENT THIS</p></td>
     </tr>
-  
     <tr>
       <td><tt>consumer_pool_size</tt></td>
       <td>1</td>
       <td>Number</td>
       <td><tt>HUTCH_CONSUMER_POOL_SIZE</tt></td>
-      <td><p>Bunny consumer work pool size</p>
-</td>
+      <td><p>Bunny consumer work pool size</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_tls</tt></td>
       <td>false</td>
       <td>Boolean</td>
       <td><tt>HUTCH_MQ_TLS</tt></td>
-      <td><p>Should TLS be used?</p>
-</td>
+      <td><p>Should TLS be used?</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_verify_peer</tt></td>
       <td>true</td>
       <td>Boolean</td>
       <td><tt>HUTCH_MQ_VERIFY_PEER</tt></td>
-      <td><p>Should SSL certificate be verified?</p>
-</td>
+      <td><p>Should SSL certificate be verified?</p></td>
     </tr>
-  
     <tr>
       <td><tt>mq_api_ssl</tt></td>
       <td>false</td>
       <td>Boolean</td>
       <td><tt>HUTCH_MQ_API_SSL</tt></td>
-      <td><p>Should SSL be used for the RabbitMQ API?</p>
-</td>
+      <td><p>Should SSL be used for the RabbitMQ API?</p></td>
     </tr>
-  
     <tr>
       <td><tt>autoload_rails</tt></td>
       <td>true</td>
       <td>Boolean</td>
       <td><tt>HUTCH_AUTOLOAD_RAILS</tt></td>
-      <td><p>Should the current Rails app directory be required?</p>
-</td>
+      <td><p>Should the current Rails app directory be required?</p></td>
     </tr>
-  
     <tr>
       <td><tt>daemonise</tt></td>
       <td>false</td>
       <td>Boolean</td>
       <td><tt>HUTCH_DAEMONISE</tt></td>
-      <td><p>Should the Hutch runner process daemonise?</p>
-</td>
+      <td><p>Should the Hutch runner process daemonise?</p></td>
     </tr>
-  
     <tr>
       <td><tt>publisher_confirms</tt></td>
       <td>false</td>
       <td>Boolean</td>
       <td><tt>HUTCH_PUBLISHER_CONFIRMS</tt></td>
-      <td><p>Should RabbitMQ publisher confirms be enabled?</p>
-</td>
+      <td><p>Should RabbitMQ publisher confirms be enabled?</p></td>
     </tr>
-  
     <tr>
       <td><tt>force_publisher_confirms</tt></td>
       <td>false</td>
       <td>Boolean</td>
       <td><tt>HUTCH_FORCE_PUBLISHER_CONFIRMS</tt></td>
-      <td><p>Enables publisher confirms, forces Hutch::Broker#wait_for_confirms for</p>
-</td>
+      <td><p>Enables publisher confirms, forces Hutch::Broker#wait_for_confirms for</p></td>
     </tr>
-  
     <tr>
       <td><tt>enable_http_api_use</tt></td>
       <td>true</td>
       <td>Boolean</td>
       <td><tt>HUTCH_ENABLE_HTTP_API_USE</tt></td>
-      <td><p>Should the RabbitMQ HTTP API be used?</p>
-</td>
+      <td><p>Should the RabbitMQ HTTP API be used?</p></td>
     </tr>
-  
     <tr>
       <td><tt>consumer_pool_abort_on_exception</tt></td>
       <td>false</td>
       <td>Boolean</td>
       <td><tt>HUTCH_CONSUMER_POOL_ABORT_ON_EXCEPTION</tt></td>
-      <td><p>Should Bunny's consumer work pool threads abort on exception.</p>
-</td>
+      <td><p>Should Bunny's consumer work pool threads abort on exception.</p></td>
     </tr>
-
     <tr>
       <td><tt>consumer_tag_prefix</tt></td>
       <td>hutch</td>
       <td>String</td>
       <td><tt>HUTCH_CONSUMER_TAG_PREFIX</tt></td>
-      <td><p>Prefix displayed on the consumers tags.</p>
-</td>
+      <td><p>Prefix displayed on the consumers tags.</p></td>
     </tr>
-  
   </tbody>
 </table>
-
-
----
-
-GoCardless ♥ open source. If you do too, come [join us](https://gocardless.com/jobs/backend_developer).