2026-02-03, 16:00–16:25, B.1.015
With the unexpected proliferation of Puppet implementations, you may be wondering how to test your modules effectively. Interestingly, this isn't a new problem. It's a somewhat known secret that even the Supported modules on the Puppet Forge weren't ever tested against Puppet Enterprise, but like Bruno we don't talk about that. Because it didn't really matter, except -- well, when it did.
That was bad enough, but now we've splintered into four separate implementations built by two wildly different groups with very different priorities. We have the legacy Open Source Puppet that's still in broad use, there's the new proprietary Puppet Core which requires a EULA and a license key to download, there's Puppet Enterprise which used to be built on OSP but will be based on Puppet Core going forward. And now we have the truly Open Source OpenVox implementation built by your friends at Vox Pupuli. They're diverging as we speak.
This talk will go over topics such as
- why it's difficult for community module authors to test their code against Puppet Core.
- why it's (was) effectively impossible to test modules against multiple implementations.
- the legal thorniness preventing Vox Pupuli from signing the EULA.
- the rough spot the ecosystem has been forced into in which paid customers were being forced into using effectively untested modules.
Many of my customers are current or former Puppet customers and they're methodically migrating from legacy OSP to OpenVox so they can keep up with security patches, project evolution, and new features. But module and gem test suites have always been written with the assumption that they only had to test against legacy OSP. Some can be tricked into running against OpenVox, but being able to test against both at the same time? Not a chance.
My customers cannot and will not accept an ecosystem with untested code, and you probably don't want to either. But you still need a way to continue testing on legacy OSP until your migration to OpenVox is complete.
We have been hard at work building a pipeline that makes this possible, with very little upstream modification. Come see how it works.
Community lead, developer advocate, and founder; I get to build neat things -and- talk to people! \o/ I've been in the tech industry in one way or another since the late 90's doing everything from devops before devops was a thing at a tiny security startup, to forensics investigations, to maintaining a compute cluster for a computational anthropology department at an American university and teaching the grad students how to write distributed Java code to run on it.
I run marathons in those funny finger shoes and my social engagement is primarily at https://hachyderm.io/@binford2k. You may have heard of that thing I'm building -- https://overlookinfratech.com.