3 ms·

Config files as copied around by scp and edited by hand are a pita -- but as checked into source control as a template and staged to machines by your deploy; th

Config files as copied around by scp and edited by hand are a pita -- but as checked into source control as a template and staged to machines by your deploy; the very simplest and most robust solution.

scarface74 10y ago
Compared to going on your Consul's website to change a value and that value automatically being updated in all of the systems?
- mattbillenstein 10y ago
  Actually yes, I want to version control that change and deploy it like I deploy code. Not blindly fire changes that I can't track into the ether.
  - tehno 10y ago
    You could always disallow consul web interface updates and have `consul kv put` scripts in SCM and validated/deployed automatically.
    - mattbillenstein 10y ago
      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...
      - awinder 10y ago
        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
- scurvy 10y ago
  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.

scarface74 10y ago

Compared to going on your Consul's website to change a value and that value automatically being updated in all of the systems?

mattbillenstein 10y ago
Actually yes, I want to version control that change and deploy it like I deploy code. Not blindly fire changes that I can't track into the ether.
- tehno 10y ago
  You could always disallow consul web interface updates and have `consul kv put` scripts in SCM and validated/deployed automatically.
  - mattbillenstein 10y ago
    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...
    - awinder 10y ago
      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
scurvy 10y ago
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.