inactivity_timeout for the vault endpoint isn't configurable/too short

[steveberryman]

We run a somewhat unconventional consul/vault setup, in that our clusters are far away from some of our servers and thus latency is pretty poor. With the hard-coded inactivity_timeout for vault of 1s here

consul-templaterb/lib/consul/async/vault_endpoint.rb

Line 234 in fa13ad2

inactivity_timeout: 1 # default connection inactivity (post-setup) timeout

consul-templaterb often times out during a run for some keys. I confirmed that increasing this to a longer time fixes the issue. Potentially somewhat of a niche request, but making this configurable would allow increase the timeout in cases where vault was a stupid distance away from the host consul-templaterb was running on.

[pierresouchay]

@steveberryman Indeed, this is pretty hardcoded... there are lots of places where we borrow parameters from the command line, would you be interested with providing a patch?

[steveberryman]

Yeah I’m sure I could do that :)

…

On 20 Aug 2021, 16:25 +0100, Pierre Souchay ***@***.***>, wrote: @steveberryman Indeed, this is pretty hardcoded... there are lots of places where we borrow parameters from the command line, would you be interested with providing a patch? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.