consul-templaterb 1.18.2 → 1.18.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d79f747c0b0378a3526f63fd7a4638f2cfe432da043821749c89f8b302a6489a
-  data.tar.gz: 69f3d665fda37542cc4496daeb77f2d300514d9708afb0eef363aebf1a5a74ad
+  metadata.gz: 6b12634693cd840c5981486ee1f2daef7b2d6a35ef3df18d726653a23d1d68a1
+  data.tar.gz: efad7e3762bf953e5029c3ddc2aa9fa8de5d06728d482f0af0679af69ad49c12
 SHA512:
-  metadata.gz: e6e24033378a8bc9abd18c6e57da606e45aac7bf20ea8f295d33ea668f2d44b9abf4395099ecf0dbc804e50a0467426807f587ba2f07fc2149361b568ce5b791
-  data.tar.gz: 4a5c613be0aee5f4c7646286b699ab3d17cf4af3b26f6e227884f14c79648d6ea3086777d547de162bd5906e161877a1c3e5f7d19c2a5ecc8d1c94a072eebcb3
+  metadata.gz: 17b0e0a59eb862d07946543bbfc170ac827ffdcdfb1c28e691e03352678abc30b7f195241fa311b66a05c263d42606bcb76d86a49445136d0ec3f7643e4cfafd
+  data.tar.gz: dd427f30e6f07cbd908cf1bab8bfd262c4fabd468dabc41fb5502264df8980813f8d40f9257fc02f4b39f14ca835368778bd375539c110734fb04d9a969f2094

data/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 ## (UNRELEASED)
 
+## 1.18.3 (September 2, 2019)
+
+BUGFIX:
+
+* When vault receives at timeout, correctly reschedule it
+
 ## 1.18.2 (August 28,  2019)
 
 BUGFIX:

data/README.md

@@ -217,11 +217,11 @@ $ consul-templaterb \\
 ### Process management and signalisation of configuration files
 
 With the `--exec` argument (can be specified multiple times), consul-templaterb will launch
-the process specified when all templates have been generated and will send a reload signal
-if the content of any of the files do change (the signal will be sent atomically however,
-meaning that if 2 results of templates are modified at the same time, the signal will be
-sent only once (it is helpful for instance if your app is using several configurations
-files that must be consistent all together).
+the process specified when all templates have been generated. When generated file(s) do change,
+a POSIX signal (HUP by default) is sent to the spawned process. If you generate several files
+at the same time, the signal will be sent only once the rendering of all templates is completed,
+so if your process is using several configuration files, all files will be modified and
+consistent before the signal is sent to process.
 
 If any template does return nothing (aka use `return nil` in the code of a template),
 consul-templaterb does consider that the template is not ready and will not launch the executable

data/lib/consul/async/vault_endpoint.rb

@@ -199,7 +199,7 @@ module Consul
         http_result = VaultHttpResponse.new(http, default_value)
         EventMachine.add_timer(retry_in) do
           yield
-          queue.push
+          queue.push(0)
         end
         @e_callbacks.each { |c| c.call(http_result) }
       end

data/lib/consul/async/version.rb

@@ -1,5 +1,5 @@
 module Consul
   module Async
-    VERSION = '1.18.2'.freeze
+    VERSION = '1.18.3'.freeze
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: consul-templaterb
 version: !ruby/object:Gem::Version
-  version: 1.18.2
+  version: 1.18.3
 platform: ruby
 authors:
 - SRE Core Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-08-28 00:00:00.000000000 Z
+date: 2019-09-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: em-http-request
@@ -261,8 +261,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.7.7
+rubygems_version: 3.0.3
 signing_key: 
 specification_version: 4
 summary: Implementation of Consul template using Ruby and .erb templating language