[Enhancement] Optional Flag for <branch>.ref File about git2consul HOT 3 CLOSED

The creation of this .ref file is internal to, and needed in, git2consul. In order for git2consul to work, it needs to know about the state of the contents for that particular path in order to perform diffs and changes. Instead of using a database or some other external state storage system, we decided to use git itself in order for git2consul to figure out changes and update KVs accordingly. Without this, git2consul would have to rewrite all KVs from that path and everything below it every time it detected a change, which is less than ideal.

from git2consul.

Thanks for the quick reply!

I figured that was the case, because our use-case is for pushing the contents of the repo on top of whatever is already in Consul, we don't have much dependence for tracking these changes outside of the repo. I'm having our job post a "curl -X DELETE" command since the path is static, I'm going to use this configuration going forward unless there's a better recommended approach for removing this file. Thanks again.

from git2consul.

@NRay7882 No problem! I think the behavior on git2consul would be to rewrite the KVs for that entire branch when it would detect a change, but I might be wrong on this one. I am going to close this, but feel free to re-open if there are any related issues that arise with your approach.

from git2consul.