@atpfm @siracusa ouch! (Original author of puppet speaking…)

First mention implied puppet was older than cfengine, when it’s the opposite - I wrote puppet after using and contributing to cfengine. (And ansible was written by someone who worked for me at puppet.)

At least puppet got three mentions! But, the last one was you saying you hated it. 😞

Oh well. It’s “owned” by a PE firm now, so if you consider it, look at OpenVox instead. Sorry it was not a fit for you!

And I agree that @marcoarment should look at one of these tools. They would add a lot of value in software distribution and configuration, not just triggering jobs.

@lkanies It’s more like PTSD from having to use it at work in a complex setup that was…not ideal.
@siracusa @lkanies I’ve been on both ends. First, an incredibly well laid out puppet setup that quite literally transformed my career and taught me how to automate and manage large fleets. 2) Inherited a puppet setup that was completely nonsensical and made me dread ever touching anything. To this day I miss puppet thanks to that first experience.
@papaschaaff @siracusa I guess that’s the mark of a powerful tool: you can build great things, or cut your foot off
@lkanies @papaschaaff @siracusa “cutting off foots every 30 minutes + splay = fqdn_rand(30)”

@siracusa heh, I totally get that. It had a tendency to let people get way too formal and complex.

I wish I could tell someone to adopt puppet today, but the world has moved on, and puppet has moved out.

Still fun to hear you mention it on the podcast, though :) not often that kind of stuff makes it into the consumer/dev space