21
IAC & DevX Updates; spring cleaning and long paths
The IAC Team processed 91 community PRs/issues across modules and tools.
We’d like to thank the following people in the Puppet Community for their contributions over this past week:
-
provision#166: “(REPLATS-169) Add a timestamp to abs job_id”, thanks to jpartlow -
puppetlabs-apache#2152: “(MODULES-11068) Allow apache::vhost ssl_honorcipherorder to take boolean parameter”, thanks to davidc -
puppetlabs-apache#2150: “support for uri for severname with use_servername_for_filenames”, thanks to Zarne -
puppetlabs-apache#2145: “(MODULES-11061) mod_security custom rule functionality”, thanks to k2patel -
puppetlabs-firewall#993: “Fixed link to REFERENCE.md”, thanks to Samgarr -
puppetlabs-postgresql#1266: “MODULES-11047 - Allow managing rights for PUBLIC role”, thanks to mtancoigne -
pdk-templates#436: “added more fine-grained control of custom_before_steps”, thanks to skoef -
pdk-templates#434: “added tags to .gitlab-ci.yml.erb”, thanks to skoef -
puppet-strings#266: “Only set tasks = true when parsing plans.”, thanks to binford2k
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-stdlib(7.1.0) -
puppetlabs-apache(6.1.0)
The following gems were released this week:
-
puppet-strings(2.7.0) -
puppet-modulebuilder(0.3.0) -
rspec-puppet(2.9.0)
We’re making good progress on the limited availability release of the new templating feature for PDK and are still on track to have this available at the end of the month. Alongside that, we released version v2.9.0 of rspec-puppet. Many thanks to David Schmitt for his help in getting this over the line!
We are very close to finish the certification for our k8s module with 1.20 version. First we added support for the new version and now we’re working with AWS for Sonobuoy k8s conformance testing, if you’re interested in how we’re doing check out the PR!
This week was really interesting. Dropsonde is a flexible framework for collecting metrics from puppet installations. Deploying this will provide insight into how modules are used for the community. We have just finished the Level of Effort and have broken down the work into small tasks to enable a successful transition. We have now started a deep dive and 2 PRs have been submitted to the dropsonde repo. Will will continue to provide weekly updates on the hottest tool currently on our plate!
We have some exciting news for you about Puppet’s support for the PowerShell DSC configuration framework for Windows. In short, content from the PowerShell Gallery will simply appear on the Puppet Forge and can be added to your Puppetfile and used just like any other Puppet module. This makes it by far the most flexible and maintainable iteration of DSC integration we’ve ever had. Pick and choose whatever DSC Resources you want and get all the VSCode IntelliSense magic you’ve come to expect. Read more on the puppet blog
During our ongoing work for integrating with DSC, we stubbed our toes hard against an old, familiar frenemy in ruby: long path support on Windows. Windows has supported paths longer than 260 characters for years now, but Ruby couldn’t ever take advantage of that. If you needed long file paths in your code, you had to specify the LFN NTFS syntax (prepending\\?\) which was… not very friendly or memorable. Luckily however, Gabriel Nagy submitted a patch to core ruby which was merged this week which just solves this problem for everyone (who uses a release of ruby which includes the patch)! As long as your modern Windows systems are configured for long path support, Ruby will now happily work with 300+ character paths, no sweat! This is huge for Windows users and developers on Ruby, which also means Windows users and developers of Puppet! We really can’t overstate what a thorn in our foot this has been how grateful we are to Gabi for resolving it.
21