Allow for Branches to be determined from ENV vars about git2consul HOT 3 CLOSED

I believe this can be done by having a different version of your configuration file for git2consul that gets deployed to your machine based on what is your target environment. Tools like Puppet, Chef, etc. can achieve this trivially.

Optionally, you can manipulate the config file dynamically with these tools. If you use Puppet, for example, the env-to-branch mapping can be dynamically set to the configuration file via templates and Puppet variables as documented here.

I don't think setting target branches with env variables is the proper approach here.

from git2consul.

The use-case for this is for a twelve-factor app dockerized git2consul container. When we build the container we copy in our default config.json that is hardcoded to poll our "dev" branch. So when this container gets deployed to a QA environment we would need a way to "override" the branches config value so that an ENV variable could be set when we start the container and git2consul would use as the branches value from ENV instead of the config branches setting.

from git2consul.

Closing this. For further explanation see #79.

from git2consul.