Ah yes. The perennial problem of managing system state with anything other than shell scripts. Many variations have been tried. Most end up being some kind of y

Ah yes. The perennial problem of managing system state with anything other than shell scripts. Many variations have been tried. Most end up being some kind of yaml based format or a custom DSL with inscrutable error messages. I don't think the answer is yet another variation on the same theme. The design space for such tools is pretty well trodden and they are all lacking in one way or another. This blog post does not say what exactly about ansible needs to be fixed and what their plan of attack is. It just sounds like the author would like a more responsive set of developers which is a social problem more than a technical one and writing yet another configuration management tool is not the right solution to that problem. Some interesting variations on that theme are http://babushka.me/ http://babushka.me/, http://larsyencken.github.io/marelle/ http://larsyencken.github.io/marelle/, https://github.com/brandonhilkert/fucking_shell_scripts https://github.com/brandonhilkert/fucking_shell_scripts, and http://palletops.com/ http://palletops.com/. I also have a variation in mind but every time I sit down to write something I remember that there are already way too many of these and instead just write another shell script.