Yeah man, I could setup a quorum of consul boxes, integrate consul's api into my application, figure out how to manage changes in that system, and then do as you say -- make a change management system to apply deltas on deploy.
Or, I could put one more file on each box in addition to the other 100,000 files I put on there...
Obviously you wouldn't choose consul for this one feature, but if you're already relying on consul as service discovery in your network, why not?
You don't need to invent a change management system, you just need to utilize from a myriad of existing consul OSS.
I'm not saying consul makes all the sense in the world for you, but there's definitely sound architectural thinking behind what the parent is talking about. It's not just a bunch of crazy talk :-D
Can consul create change log trails to keep the auditors happy? Some of us are working in environments that require more rigor than a pet project.
Not throwing stones, a serious question. Made a few decisions to favor log files and change control systems vs a web app that had ACL's but no real auditing or change control mechanisms.
