4 ms·
http://flabbergast.org/ http://flabbergast.org/ is the closest, and in a similar vein you'd have https://github.com/google/jsonnet https://github.com/google/jso
by bbrazil 11y ago
http://flabbergast.org/ http://flabbergast.org/ is the closest, and in a similar vein you'd have https://github.com/google/jsonnet https://github.com/google/jsonnet and then Nix.
Configuration management is a very different thing to what most of ansible/chef/puppet/salt are commonly used for - it's possible to do it but it's a bit of an uphill battle.
The core problem of config management is not pushing out things, but rather how do you represent configs with their myriad of interacting multi-level exceptions while also allowing tens/hundreds/thousands of operational changes to be ongoing at the same time.
Ansible for example is good for about 3-4 levels of exceptions, which isn't that much considering region and environment (dev vs prod) are two of those.
- arde 11y agoFlabbergast seems to have the right idea, but its lack of examples is a problem. Its only example is based around Apache Aurora (who in hell uses that and wtf it is I don't know, and I don't really want to learn that just to understand an example). This hasn't changed since it was first announced, so I don't think I'll take another look at it for quite a while unless I come by some reasonable howto.