We’d like to thank the following people in the Puppet Community for their contributions over this past week:
puppetlabs-docker#707: “(docs) update README.md”, thanks to vladdoster
puppetlabs-kubernetes#470: “Add etcd_listen_metric_urls parameter”, thanks to treydock
puppetlabs-kubernetes#462: “Allow tmp_directory to be changed”, thanks to treydock
puppetlabs-postgresql#1226: “Fix postgresql::sql task when password is not set”, thanks to smortex
puppetlabs-postgresql#1225: “Clean up globals logic to support CentOS 8 stream”, thanks to ekohl
puppetlabs-postgresql#1230: “(bug) fix systemd daemon-reload order when updating service files”, thanks to vchepkov and ekohl for raising the issue and great cooperation on the PR!
pdk#939: “(MAINT) Disable parallel unit package testing specs on Windows”, thanks to scotje
pdk#932: “Add ability to generate functions”, thanks to logicminds
pdk-vanagon#274: “Revert “Only install system_tests gem on the main ruby””, thanks to scotje
ruby-pwsh#101: “(MAINT) Place nil check when assigning is_same”, thanks to bwilcox
ruby-pwsh#96: “(MAINT) Ensure is_same check works for nil manifest values”, thanks to bwilcox
Check all the ways to reach us if you want to directly contact us about anything module related.
New Module / Gem Releases
The following modules were released this week:
This week the development work was focused on the automated release preparation and multi-node testing.
The template for the automated module release preparation in
pdk-templates is currently undergoing testing and, hopefully, by the end of next week a pdksync across all our supported modules will ease releases in the future.
For a quick preview on multi-node testing, take a look at this NTP pull request that deploys two VMs on GCP with different roles and runs an integration test suite to check communications.
Over the last two weeks we’ve released several small iterative improvements to our
Puppet.Dsc PowerShell Module and the
puppetlabs-pwshlib Puppet module as we draw towards closing out our first major milestone.
As part of this effort, we published two new blog posts; one on troubleshooting Puppetized DSC modules and another by Paula on migrating from
puppetlabs-dsc to the Puppetized
The troubleshooting document has already paid off, leading to the filing of excellent bug reports and even a bugfix PR independent of the IAC team by Bill Wilcox.
It also led to a pairing session with Jordan Bush where he was able to discover and file a repro for a bug in
xDnsServerDiagnostics in the xDnsServer PowerShell module.
We’re excited to see the adoption of the Puppetized modules in the
dsc namespace on the Forge grow, especially now that we’ve cut down on some of the guess work for migrating from the older
The last remaining tasks in our first milestone are administrative, so next week will see us tackling issues in the next milestone which should set us up for a
Check out the new nightly builds (use the
puppet6-nightly repos for now) of the PDK with ruby 2.7, facter 4 and puppet 7. Please note that this is also dropping puppet 4 and hence will become PDK 2.0 at some point in the near future.
Despite the travel restrictions, the wider ecosystem group at Puppet came together this week to share challenges, ideas, and plans. While we can’t share many of the details (yet!!), it was a great opportunity to exchange with our friends from the Forge, Bolt, Integrations, and Solution teams, as well as update our understanding of how our work fits into the greater Puppet Product Strategy. Big shout-out to Ben Ford for stepping up to the role of Product Manager and organising a week chock-full of Content!
Last week, David Swan addressed a long-standing issue where litmus would get confused about exit codes when running puppet. This week saw a minor adjustment and another litmus release to make this also work for the