blue_green_workers 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 763c209e7bb28f7c8e3753cc57d4f3e9d0b1c021
-  data.tar.gz: 1afcd620a1b05e054f56300f0dbdecd0d7509c50
+  metadata.gz: 9bb20f810be71613d35898d0ec1998b6060a3594
+  data.tar.gz: 148fd9daf814872e616b5baddf9830bf98a3e033
 SHA512:
-  metadata.gz: fc6b12114e9d32012f262e85fc34f87bb073edfad3ac36d7c846348b7c483db0a22300bdfc407b64c88a3ae74293caf106cac54860605f9800be86bb201cf620
-  data.tar.gz: fd9be9b4151d112db6af2eaffb8d4cacf25e1382f86c8c205dc77f0f2c7a1d77639a10ecca8762db659720ea6f72d80198e49b24c3fdfbad04d4ec622747765f
+  metadata.gz: 91db6ce2cf44a74f1385cbd5c768a6512879613de21bd6ee760e8b000356831beb028b9bbae12aeac7ba31a243f2a6b1482b683ff112a343b817f4d8a9f2be53
+  data.tar.gz: 1c5a2b5a1a89a0d84351c0470c65319becc7f6bfaf41142bb878c678d6b40f7035bc4a448b6bf3a059076320c5ca02209bb6fba9838480eafbaaf80c145b67a6

data/README.md

@@ -25,6 +25,7 @@ This gem doesn't attempt to provide an interface through which you specify which
 BlueGreenWorkers.configure do |config|
   config.cluster_name = 'blue'
   config.determine_active_cluster { ActiveCluster.first.value }
+  config.refresh_interval = 10
   config.activate { QueueClient.listen! }
   config.deactivate { QueueClient.shutdown! }
   config.logger = Logger.new STDOUT
@@ -33,7 +34,7 @@ end
 
 * `cluster_name` - Defines the name for this cluster.  Something like `ENV['CLUSTER_NAME']` probably makes sense
 * `determine_active_cluster` - Takes a block that returns the name of the current active cluster
-* `refresh_interval` (optional) - How often to cache the active cluster, `0` (the default) will call the block passed to `determine_active_cluster` every time a worker is executed.
+* `refresh_interval` (optional) - How often to cache the active cluster in seconds, `0` (the default) will call the block passed to `determine_active_cluster` every time a worker is executed.
 * `activate` (optiona) - Block to call when this cluster goes active.  Will be called during initialization.  `refresh_interval` must be specified.
 * `deactivate` (optiona) - Block to call when this cluster goes passive.  This block will not be called if the cluster is started in passive mode.  `refresh_interval` must be specified.
 * `logger` (optiona) - Logger to use
@@ -44,13 +45,16 @@ In addition to attaching event handles to `activate` and `deactivate` you can al
 
 ```ruby
 loop do
-  BlueGreenWorkers.execute do
+  BlueGreenWorkers.execute(opts) do
     # Do some work, poll for stuff, etc
   end
   sleep 60
 end
 ```
 
+Options include*
+`delay` -- Delay for `n` seconds if we're not the active cluster
+
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.

data/lib/blue_green_workers.rb

@@ -21,11 +21,12 @@ module BlueGreenWorkers
     config.validate
   end
 
-  def self.execute
+  def self.execute(opts = {})
     if config.active_cluster_block.call == config.cluster_name
       yield
     else
       logger.debug 'Workers not active, skipping BlueGreenWorkers#execute'
+      opts[:delay] && sleep(opts[:delay])
     end
   end
 

data/lib/blue_green_workers/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module BlueGreenWorkers
-  VERSION = '0.1.0'
+  VERSION = '0.2.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: blue_green_workers
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - hawknewton