action_subscriber 4.0.1 → 4.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3a06cad234357e4194584f11c8b6ea3525ea14f2
-  data.tar.gz: 796c79df7cd3a5a3d74564bfa4c21632aaf83fa8
+  metadata.gz: 7b0844296458260c50c20826245f5a783ed80c45
+  data.tar.gz: 70f905d4084445c9bd6acacc0a7fe487081c1abb
 SHA512:
-  metadata.gz: 65460f70236d3d4a0bb9318c8653ae74b3dddb703ffc8d12426111648c12d692b741ead806265eca4c52d417cdb62736ec8b570dcad6e2b13f69758e704d5f93
-  data.tar.gz: dfa68d0a77ff67ecc5be071d5e5591558ab93e9d0f8f02164f9012c277e05c9254e7303ef279e9a486b709c5179113ab6fe0a78c7892995494eaaf90a2285208
+  metadata.gz: b43e261bf03707d66ba31e8bc260fa9424b547f3de5ed86bc39741b2486a3314d856707ac19b88d8965e1cbf7868cc7c3996d29d4f85830d9d9a4f0f8ccc6697
+  data.tar.gz: 511a595019bd2f6c6d410cea15dbd56f144dc8b9535fd18319f9541a6b20551e8f51e1bd7e7076787dc5110d0a66adc1e74476cea5f89b88b322cdbaa94d0e7b

data/.travis.yml

@@ -1,9 +1,9 @@
 language: ruby
 rvm:
- - 2.2.4
- - 2.3.0
- - jruby-9.0.4.0
- - jruby-9.1.5.0
+ - 2.2.6
+ - 2.3.3
+ - jruby-9.0.5.0
+ - jruby-9.1.7.0
  - jruby-head
 services:
  - rabbitmq

data/README.md

@@ -108,6 +108,13 @@ Other configuration options include :
 * config.hosts - an array of hostnames in your cluster (ie `["rabbit1.myapp.com", "rabbit2.myapp.com"]`)
 * config.threadpool_size - set the number of threads availiable to action_subscriber
 * config.timeout - how many seconds to allow rabbit to respond before timing out
+* config.tls - true/false whether to use TLS when connecting to the server
+* config.tls_ca_certificats - a list of ca certificates to use for verifying the servers TLS certificate
+* config.tls_cert - a client certificate to use during the TLS handshake
+* config.tls_key - a key to use during the TLS handshake
+* config.verify_peer - whether to attempt to validate the server's TLS certificate
+
+> Note: TLS is not handled identically in `bunny` and `march_hare`. The configuration options we provide are passed through as provided. For details on expected behavior please check the `bunny` or `march_hare` documentation based on whether you are running in MRI or jRuby.
 
 Message Acknowledgment
 ----------------------
@@ -155,3 +162,20 @@ easily test your public methods without dependence on data from Rabbit.  You can
 optionally pass data for your mock subscriber to consume if you wish.
 
 ``` subject { mock_subscriber(:header => "test_header", :payload => "payload") } ```
+
+Development
+===========
+
+If you want to work on `action_subscriber` you will need to have a rabbitmq instance running locally on port 5672 with a management plugin enabled on port 15672. Usually the easiest way to accomplish this is to use docker and run the command:
+
+```
+$ docker run --net=host --rm=true --hostname diagon --name rabbit rabbitmq:3.6.6-management
+```
+
+Now that rabbitmq is running you can clone this project and run:
+
+```
+$ cd action_subscriber
+$ bundle install
+$ bundle exec rspec
+```

data/lib/action_subscriber/configuration.rb

@@ -14,9 +14,14 @@ module ActionSubscriber
                   :port,
                   :prefetch,
                   :seconds_to_wait_for_graceful_shutdown,
-                  :username,
                   :threadpool_size,
                   :timeout,
+                  :tls,
+                  :tls_ca_certificates,
+                  :tls_cert,
+                  :tls_key,
+                  :username,
+                  :verify_peer,
                   :virtual_host
 
     CONFIGURATION_MUTEX = ::Mutex.new
@@ -32,6 +37,7 @@ module ActionSubscriber
       :seconds_to_wait_for_graceful_shutdown => 30,
       :threadpool_size => 8,
       :timeout => 1,
+      :tls => false,
       :username => "guest",
       :password => "guest",
       :virtual_host => "/"

data/lib/action_subscriber/rabbit_connection.rb

@@ -69,7 +69,12 @@ module ActionSubscriber
         :port                          => ::ActionSubscriber.configuration.port,
         :recover_from_connection_close => true,
         :threadpool_size               => ::ActionSubscriber.configuration.threadpool_size,
+        :tls                           => ::ActionSubscriber.configuration.tls,
+        :tls_ca_certificates           => ::ActionSubscriber.configuration.tls_ca_certificates,
+        :tls_cert                      => ::ActionSubscriber.configuration.tls_cert,
+        :tls_key                       => ::ActionSubscriber.configuration.tls_key,
         :user                          => ::ActionSubscriber.configuration.username,
+        :verify_peer                   => ::ActionSubscriber.configuration.verify_peer,
         :vhost                         => ::ActionSubscriber.configuration.virtual_host,
       }
     end

data/lib/action_subscriber/version.rb

@@ -1,3 +1,3 @@
 module ActionSubscriber
-  VERSION = "4.0.1"
+  VERSION = "4.1.0"
 end

data/spec/lib/action_subscriber/configuration_spec.rb

@@ -9,6 +9,7 @@ describe ::ActionSubscriber::Configuration do
     specify { expect(subject.seconds_to_wait_for_graceful_shutdown).to eq(30) }
     specify { expect(subject.threadpool_size).to eq(8) }
     specify { expect(subject.timeout).to eq(1) }
+    specify { expect(subject.tls).to eq(false) }
   end
 
   describe "add_decoder" do

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: action_subscriber
 version: !ruby/object:Gem::Version
-  version: 4.0.1
+  version: 4.1.0
 platform: ruby
 authors:
 - Brian Stien
@@ -12,7 +12,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-11-21 00:00:00.000000000 Z
+date: 2017-01-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -268,7 +268,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.5.1
+rubygems_version: 2.6.10
 signing_key: 
 specification_version: 4
 summary: ActionSubscriber is a DSL that allows a rails app to consume messages from