Get Puppet Enterprise First 10 nodes are free!
Try it now
Request a demo
Automate IT and infrastructure, manage complex workflows, and mitigate risk at scale.
Try the full-featured Puppet Enterprise for free on 10 nodes.
Puppet Comply Find and prevent compliance failures
Compliance EnforcementRemediate to stay in compliance
Continuous Delivery for Puppet Enterprise Build, test, and deploy infrastructure as code faster and easier
Content & Modules Pre-built scripts to automate common tasks
CentOS EOL Here’s how to secure your CentOS infrastructure – even after EOL.
Find thousands of component modules built by the community and guidance on using them in your own infrastructure.
Visit Puppet Forge >>
Open Source PuppetPerfect for individuals and small infrastructure
BoltAutomate tasks in orchestration workflows
See all open source projects >>
Contribute to open source projects >>
From its inception to today, we get a lot of questions about the past and future of the Puppet Developer Kit (PDK). In this article, we will provide a few answers to the most common questions, as well as a roadmap ahead.
Table of Contents:
The Puppet Developer Kit was launched to help our users develop high quality modules faster and over the years, it has seen regular development towards that goal.
The Puppet Developer Kit was launched in 2017 to be a single install that would provide everything you needed to write, lint, test and publish a Puppet module — and for the most part, that's what it did.
The PDK did exactly what it set out to do. It enabled users of Puppet and its ecosystem — regardless of experience level — to create Modules that were testable, deployable, and shareable. It provided functionality to keep those modules running against all supported Puppet versions, as well as the core Gemset to run all the features built into the template.
In order for all this to work, the PDK hinged on that single template which was maintained by the Puppet Developer Experience (PDE) team.
Since its launch, the PDK has come to support the creation of more than just modules and classes. With each successive addition, the template and the packaging system had to support more dependencies, and these dependencies needed to be monitored and updated in line with Puppet agent support and things like security fixes.
This overhead meant the PDK couldn’t move forward quickly in supporting the wealth of content our users wanted. And every new feature made the template system much more complex and awkward to customize for your own needs.
There are a few things that you can look forward to for PDK:
Our priority is to meet the needs of PDK users. We want to better understand who uses PDK, why they are using it, and what they are looking for to make PDK functional and effective.
The work that was done on PCT and PRM deserves a shout out — it took time, it took effort, and it was no small feat. We appreciate everyone who contributed to both PCT and PRM —thank you.
With that excellent work as a foundation, we took the learnings from the PCT design as a foundation for the future of PDK. Almost all of the patterns will ideally be ported back in to PDK to form the new pdk-templates.
You can visit the PCT and PRM toy chests to revisit past work.
Feedback is so important to us. Our team would love to engage with our community about our roadmap and we hope that you can see yourself using these tools in the future. Your feedback can have a real impact on what we build.
To get in touch, the CAT Office Hours are every Tuesday at 3pm GMT. Outside of those hours, other members within the Puppet Slack community may be able to help!
You can also check out our Puppet Community Calendar for the latest community events and other ways to stay in touch with Puppet.
Participate in the PDK Community:
GET SUPPORT FOR PDK FROM PUPPET
This article has been revised in April 2023 for accuracy and the latest information about PDK.
Puppet by Perforce Principal Software Engineer
Craig Gumbley is the Principal Software Engineer at Puppet by Perforce.