beetle 3.0.0.rc2 → 3.0.0.rc4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fb0489f8580ec11b65b79718c9e76c0f4b26a14af2fbbf471cf4b630fca5fa7d
-  data.tar.gz: 0f3ef313bfaf103eecfd1c1714c5d28b6ec10bc7ce0313e55f0cee6e00f2086a
+  metadata.gz: '099a52ef69ab0d75ed3027dc22154f482e4595c2d259117af8b5be4db556e832'
+  data.tar.gz: 5deea72b588ba0cef6666641b41a66c7bcffd2b479dc7dbfe2abd6c835d067d5
 SHA512:
-  metadata.gz: 51aa8c7058c8149daa6c2d69c1ae8a26731957290f06e4bde26a06613e260030f9cb16d286415958db74afcb38bdc74a9ccacc58643ceb25227662a800fada22
-  data.tar.gz: ae1eed22b04f81c612aff1ad88836e57df2db997a923da8f1819d8675093a9533f377e6429928049f9665b5a7548cdbbfb48172ddfbb361bac2e2adbcfba507b
+  metadata.gz: 5368bd7b2c9fd9f910d5068ca95f9be7d44b4b09bbbf94c2a14ba8f692a3d13fc4b47595bf7f0256a0a488a0ee5feb319370271e620ccc6ab4df5dcbc7bb2ca0
+  data.tar.gz: 1f06cbdaa672e7bf68d58506dde08efbb0310c34937881b1b8ec0abb73a149bf48b3706eacf3c4a241fddbb91c8062e067c594e6bf7b7ef2b57f40f314342e4c

data/README.rdoc

@@ -121,8 +121,7 @@ distribution.
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Hack along and test your code using rake test and rake
-   cucumber. You must start consul in order to use cucumber.
+3. Hack along and test your code.
 4. Commit your changes (`git commit -am 'Add some feature'`)
 5. Push to the branch (`git push origin my-new-feature`)
 6. Create new Pull Request
@@ -130,6 +129,37 @@ distribution.
 Don't increase the gem version in your pull requests. It will be done after merging the request,
 to allow merging of pull requests in a flexible order.
 
+== Running the tests
+
+Beetle ships with a cucumber feature to test the automatic redis failover
+as an integration test.
+
+To run it, you have to start a RabbitMQ server and a consul
+development mode.
+
+The top level Rakefile comes with targets to start several RabbitMQ
+instances locally.  Make sure the corresponding binaries are in your
+search path. Open two shell windows and execute the following command:
+
+    rake rabbit:start1
+
+and
+
+   rake consul:start
+
+Then you can run the cucumber feature by running:
+
+    cucumber
+
+or
+
+    rake cucumber
+
+
+Note: Cucumber will automatically run after the unit test when you run rake.
+
+
+
 == How to release a new gem version
 
 Update RELEASE_NOTES.rdoc!

data/RELEASE_NOTES.rdoc

@@ -1,5 +1,9 @@
 = Release Notes
 
+== Version 3.0.0.rc3
+* store redis gc stats in redis and display them in the configuration
+  server web UI
+
 == Version 3.0.0.rc2
 * change policy setup to be asynchronous, on demand in publisher and
   consumer. Users have to run a processors to listen to messages and
@@ -9,6 +13,10 @@
   expiry times.
 * added delete_queue_keys command to beetle to allow deletion of
   excess dedup store entries for a given queue.
+* config server: store current master server in consul, if consul
+  config has been provided.
+* config server: server correctly updates configured client ids when
+  they change in consul.
 
 == Version 3.0.0.rc1
 * provide client method to setup queues and queue policies.

data/Rakefile

@@ -83,10 +83,10 @@ namespace :redis do
 end
 
 namespace :consul do
-    desc "start consul agent in development mode"
-    task :start do
-      system "consul agent -dev -node machine"
-    end
+  desc "start consul agent in development mode"
+  task :start do
+    system "consul agent -dev -node machine"
+  end
 end
 
 Cucumber::Rake::Task.new(:cucumber) do |t|

data/lib/beetle/version.rb

@@ -1,3 +1,3 @@
 module Beetle
-  VERSION = "3.0.0.rc2"
+  VERSION = "3.0.0.rc4"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: beetle
 version: !ruby/object:Gem::Version
-  version: 3.0.0.rc2
+  version: 3.0.0.rc4
 platform: ruby
 authors:
 - Stefan Kaes
@@ -12,7 +12,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-05-13 00:00:00.000000000 Z
+date: 2019-05-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bunny
@@ -299,7 +299,6 @@ email: opensource@xing.com
 executables: []
 extensions: []
 extra_rdoc_files:
-- features/README.rdoc
 - RELEASE_NOTES.rdoc
 - examples/README.rdoc
 - REDIS_AUTO_FAILOVER.rdoc
@@ -328,7 +327,6 @@ files:
 - examples/redundant.rb
 - examples/rpc.rb
 - examples/simple.rb
-- features/README.rdoc
 - features/redis_auto_failover.feature
 - features/step_definitions/redis_auto_failover_steps.rb
 - features/support/beetle_handler

data/features/README.rdoc

@@ -1,23 +0,0 @@
-=== Cucumber
-
-Beetle ships with a cucumber feature to test the automatic redis failover
-as an integration test.
-
-To run it, you have to start a RabbitMQ.
-
-The top level Rakefile comes with targets to start several RabbitMQ instances locally.
-Make sure the corresponding binaries are in your search path. Open a new shell
-and execute the following command:
-
-    rake rabbit:start1
-
-Then you can run the cucumber feature by running:
-
-    cucumber
-
-or
-
-    rake cucumber
-
-
-Note: Cucumber will automatically run after the unit test when you run rake.