3 ms·
You can't, for example, write a tool to safely update a config file to work with a new version of the software You never can tell the future. This is a straw m
by contingencies 12y ago
You can't, for example, write a tool to safely update a config file to work with a new version of the software
You never can tell the future. This is a straw man.
apply some specific update across a bunch of machines
This is a bad idea anyway: the immutable server model seems to have been recognized as the way forward. See https://news.ycombinator.com/item?id=6705269 https://news.ycombinator.com/item?id=6705269 for reasoning.
or to catalogue the configurations each machine has
Again, immutable servers make this pointless.
I think, overall, given your examples you are clearly looking at the wrong tool (ssh or whatever plus systemd; a host-centric combined init system, process manager, log manager, and whatever else) for the job (managing multiple machines in disparate states).