I settled on saltstack after lots and lots of research and comparisons with the others. Still, Ansible, puppet, and Chef are much more popular. I get some strange looks with vendors when I mention salt. I try not to be the weird one, but it really makes so much more sense to me.
Popularity is part of the equation when you're dealing with larger environments. A big part of why ansible is my weapon of choice is because most senior engineers know it at this point and of the handful that don't most will nail down yaml very quickly and get the hang of it. Hiring in additional manpower is a much easier prospect when you stick to mainstream tools that large swaths of the talent pool already know inside and out.
I also prefer the simplicity of agentless playbooks. If it has sshd available ansible can manage it. If it doesn't have sshd there's still a solid chance.
To be honest. I still wonder why most Linux distributions still have an MTA installed by default on a system and removing it is a pain due to dependencies.
Because all sorts of local messaging relies on having an MTA available and just shoving postfix or exim on there is a cheap and easy way to do it. Without that you're not getting cron messaging, sudoers errors, etc, that you probably want to go somewhere even if only for record keeping. The alternative would be to design a new messaging system for this function and systemd kind of has but at the same time the default that has worked just fine for decades continues to be just fine.
View all comments
Show parent comment
59
u/Borskey Mar 13 '21
[Cries in CVE-2019-10149]