15
IAC & DevX Status Updates; it's a marathon, not a sprint
We’d like to thank the following people in the Puppet Community for their contributions over this past week:
-
puppetlabs-docker#740: “Allow management of the docker-ce-cli package”, thanks to kenyon -
puppetlabs-iis#325: “Correct error handling in require ruby-pwsh”, thanks to benningm -
puppetlabs-inifile#454: “Accept Datatype Sensitive”, thanks to cocker-cc -
puppetlabs-java_ks#373: “Accept Datatype Sensitive for Secrets”, thanks to cocker-cc -
puppetlabs-java_ks#372: “Fix fingerprint comparison”, thanks to kdehairy and the following people who helped get it over the line (creativefre)
Check all the ways to reach us if you want to directly contact us about anything module related.
The following modules were released this week:
-
puppetlabs-docker(4.1.0) -
puppetlabs-inifile(5.1.0) -
puppetlabs-java_ks(4.1.0) -
puppetlabs-iis(8.0.3) -
puppetlabs-helm(4.0.0) -
ruby-pwsh(0.9.0) -
Puppet.Dsc(0.6.0)
We had a great community day this week and processed 28 issues and PRs across our supported modules and tooling. And a shout out again to cocker-cc for their continued engagement in adding Sensitive Datatype support to more modules.
We’re very happy to announce that we finished running the conformance tests for v1.20 on our kubernetes module. Its official, our supported Kubernetes Puppet module is a certified installer for Kubernetes v1.20. It was a long journey with a lot of lessons, first about k8s components and workflow, but also about how to approach each situation and invest the time. If you’re curious about the process, you can find our PR on the cncf repository.
Puppet’s Partner Integrations (PIE) Team have successfully ported the tests to run on Cloud CI and configured the repository to use our Automated Release Workflow. Thanks to Bill Hurt and Sharon Nam for the collaboration opportunity.
The new DSC module builder is inching ever closer to the finish line and the 1.0 release with an automated publishing pipeline is in sight. This required coordinated efforts all across our teams, involving everything from Michael’s relentless persistence to Josh’s assistance with some core Puppet updates to support imprecise DSC Resources, all the way to Gabi’s journey to add Windows long path support to upstream Ruby itself. This has been a marathon, with all sorts of new challenges discovered along the way, but thanks to everyone’s hard work we’re nearly there.
15