Hi, we made configtailor to manage the growing number of JSON config files that we managed for every environment and cell that we maintained.<p>configtailor generates config files based on any dimension that you input. For example, we have cells (us0, us1, ..., us9) and we have microservices. For internal microservice discovery we use DNS with the following URI `us0.microservice.path`. We were copying and pasting into each cell's config file the path per cell along with dev and test environments. With configtailor we can put in `$cell.microservice.path` and have configtailor generat the appropriate config.<p>Some other benefits:
- Easily set config values that can be reused in each environment. For example, setting a base config value that is only overwritten for tests.
- Hooks into what people are used to with other Go tools that generate other files.<p>Overall, I was excited to open source this because our config files were a copy/paste nightmare and this tool helped us keep our config DRY and prevents people from missing values.<p>Let me know what you think!