There has been a significant change in the Open Source landscape of Puppet in recent months, I will not go too much into the details but suffice to say that Perforce (Puppet trademark owner) have essentially created a private closed-source fork of Puppet and from now on if you get “puppet” packages they are this rogue closed source fork.
Updates to the closed source fork will not automatically be done to the community repositories, there’s is no undertaking that the updates, when they are made, will be complete or reflect what is in the private fork.
Some relevant blog posts:
At this point, any Perforce Puppet release is a high-risk, closed source fork, I do not suggest anyone keep using these packages as you are essentially running closed source disguised as Open Source. You will not be able to see git history of what you are running, you will not be able to see build tooling or related infrastructure.
This left the community in a lurch, but luckily the good people from Vox Pupuli has come to the rescue and now hosts the only actually Open Source implementation of the Puppet Specification called Open Vox. There has also been significant build pipeline work which is now entirely open and visible to everyone - a significant strengthening of the Open Source commitment.
Some relevant blog posts:
Going forward there will be no way to test Choria against the rogue fork of Puppet that Perforce maintains without signing an EULA (as yet unseen by anyone). There will also be limits to how many open source servers one may manage (25).
As such, Choria will not continue to support the rogue fork of Puppet that Perforce maintains and will take steps in future releases to require Open Vox.
Read on for some timelines and release details.
[Read More]