We’d like to thank the following people in the Puppet Community for their contributions over this past week:
puppetlabs-docker#666: “Fix misplaced backslash in start template”, thanks to optiz0r
puppetlabs-mysql#1334: “(MODULES-10788) - fix for password prompt when creating mysql_login_path resource”, thanks to andeman
facterdb#160: “Fixes a bug with generate_filter_str”, thanks to logicminds
facterdb#159: “Fixes #19 - add filter validation”, thanks to logicminds
pdk#916: “(MAINT) Switch default pdk-templates branch to
main”, thanks to scotje
pdk-templates#351: “(#350) Update deprecated globals”, thanks to silug
pdk-vanagon#267: “(MAINT) Make it easier to test non-tagged puppet-runtime builds”, thanks to scotje
puppet_litmus#324: “Add write_file helper”, thanks to RandomNoun7
rspec-puppet#806: “(MAINT) Use Appveyor 2019 image for Ruby 2.7/Windows testing”, thanks to scotje
rspec-puppet#805: “ coverage.rb: Fix handling of 0 total resources”, thanks to scotje
rspec-puppet#799: “Add 2.7.10 release to changelog”, thanks to scotje
New Module / Gem Releases
The following modules were released this week:
Life of an intern at Puppet
Puppet 7 Nightly Testing
As part of our progress to a stable Puppet 7 platform release, we are now expanding our Puppet 7 nightly build tests to all supported modules.
A big thank you to the Nights Watch team, specifically, Florin, Gimmy and Oana for their help in debugging an issue in the
As hinted before we are working on a public cloud-based acceptance testing solution for the puppet modules we maintain. One of the big problems over the years was that our internal testing results were not available for our community contributors. This locked up our investment in testing inside the corporate VPN and did not help community contributors.
This is about to change. Today we had the first public (test-)pull request run unit and acceptance tests on entirely public infrastructure and report the results in public. As we roll out the new jobs to all our modules and all our platforms, you’ll be start to see the test results show up on PRs and on a schedule checking against environmental drift. Over the next weeks we’ll also work on batting down the hatches and tidying up the code base to allow us run a smooth and reliable platform. Expect more detailed blog posts and announcements as we continue to progress towards a production-ready stable service.
As part of that work, we submitted some work and bug reports to upstream repos: