Calvin Leung Huang

Did some quick visual stack tracking and problem seems to likely stem from `Branch.prototype.handleRefChange()` -> `Branch.prototype.pull()` -> `getLastProcessedRef()` -> `consul.kv.get()`. `handleRefChange()` should perform retries on consul-related error instead for purging...

@samifruit514 you are right, it seems that the exception is thrown by `consul.kv.del()`. 0. The consul network experiences a hiccup during polling. 1. git2consul triggers a cache purge. 2. Local...

You might be able to achieve what you are looking for by using git2consul + [gosecret](https://github.com/Cimpress-MCP/gosecret) + [fsconsul](https://github.com/Cimpress-MCP/fsconsul). For a more detailed example, the gosecret [readme](https://github.com/Cimpress-MCP/gosecret#how-it-works) provides a similar scenario...

Can you include the actual logs for more information?

This is probably due to the default `maxBuffer` being exceeded. It should solved by explicitly bumping up the value, specifically in [command.js](https://github.com/Cimpress-MCP/git2consul/blob/c74e0ea328effd31f378053e7f43a60724c37027/lib/git/commands.js#L12). `exec` should be changed to the following: ```...

According to [this Stackoverflow post](http://stackoverflow.com/questions/20417118/using-node-js-i-get-error-eisdir-read), `ESDIR` is caused by a mismatch in expected and actual file type. In your case, it's triggering on `/tmp/git2consul/master/`

@XerxesDGreat to answer your question, the usual scenario is that git2consul runs on the target datacenter. In our case, we use consul-replicate to move KV data from one DC to...

That's correct. From a technical point of view this can be implemented, but there are available solutions and there was no compelling use case/scenario for this. We can include it...

Feel free to submit a PR with the changes and we can take a look at it!

@spanktar Yes, it is being considered. We are working refactor of git2consul to include file backends, but there is no ETA on this yet. Apologies for the delay! Edit: If...