Puppet is actually a very competent infrastructure-as-code tool. I never liked the typical architecture where you run a few central puppetmaster nodes with hun

Puppet is actually a very competent infrastructure-as-code tool. I never liked the typical architecture where you run a few central puppetmaster nodes with hundreds or thousands of puppet agents all syncing to that... There are other ways to use the tool, however. In contrast with a centralized infrastructure, it's also possible to just collect a few puppet manifests in git, then you simply clone the repo and run `puppet apply` on demand. Puppet is still a powerful language for declarative representation of system configuration. Works to apply a specific configuration at a specific time or as a way to automate the construction of VM images. One place puppet excels is when you want to reuse a bit of configuration in bare metal, virtual machine or container images. With puppet you can pretty easily generate all three from one source of truth with minimal special-cases for the config variants. All that being said, I haven't reached for puppet as my first choice tool in quite some time. Maybe time to change that and give OpenVox a look. It'll be a win if OpenVox saves me from further suffering through the indignity of working with Ansible.