Consul-Conf: config templates from consul data

Object oriented mechanism to rewrite config files from template filled in by consul data.  The primary functionality here is to go through the consul services and nodes, using their health checks to come up with an idea of what nodes offer what servies  and their health status.  This data can then be plugged into  template to write out a configuration file. The code includes a diffing mechanism to verify that the file has changed, with comment exclusion, and hooks eg to restart services.
I suspect this is do some caching internally to this tool? But why would you end up getting healthChecks for the same `node` more than once? Plus, I think you're optimizing something here that wouldn't be that big of a deal.