VERSION 3.14.1 *in this release*
*Due to an issue during the release process, Bolt 3.14.0 was not released. ✨ *new features* - Calling the wait() plan function without a list of Futures will now wait on all Futures created so far in the plan. - Bolt now ships with the latest version of the http_request module, which includes support for making patch requests. - YAML plans now support a verbose step that prints a message when run in verbose mode. - The out::message & out::verbose plan functions now log messages at the info and debug levels respectively. - Bolt now supports showing detailed information about a module using the bolt module show <module> command and Get-BoltModule -Name <module> PowerShell cmdlet. - The native-ssh transport has a new batch-mode configuration option that can be used to enable or disable BatchMode. For more information, see the documentation <https://puppet.com/docs/bolt/latest/troubleshooting.html#providing-a-password-non-interactively-using-native-ssh> . - Bolt now prints a more readable message for plan results that are Bolt datatypes when using the human output format. 🔧 *bug fixes* - Bolt no longer displays a warning about analytics collection when analytics is disabled and the analytics.yaml file does not exist. 🚨 *removals* - Bolt no longer supports Fedora 30, Fedora 31, or MacOS 10.14 (Mojave). VIEW FULL RELEASE NOTES <https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md> *in the works* - Support for clearing the plan and task caches. - Support for using the _catch_errors metaparameter in the apply_prep plan function *nuts and bolts* Each month, we'll highlight a different Bolt feature and cover the details on what it is, why you might want to use it, and how it can be used in your workflows. July's highlighted feature is: *BoltSpec*! *What is BoltSpec?* BoltSpec is a library of helpers that ships with Bolt. It is intended to be used with RSpec, a testing tool, to write unit tests for your plans. Specifically, BoltSpec's helpers let you test the behavior of your plans without the need to connect to targets. *Why should I use BoltSpec?* Because plans can include complex logic that automates different jobs, it's important to test that the plan behaves as you expect. BoltSpec lets you easily write tests for your plans so you can test their behavior in development and catch any errors before your plans are used in production. Also, because BoltSpec stubs out Bolt functions that connect to targets, you don't need to worry about provisioning containers or VMs to run these tests. *How do I use BoltSpec?* Using BoltSpec is as easy as installing and configuring rspec-puppet for your module or project, and then adding a couple lines to your tests' configuration file. If you already develop Puppet modules using the Puppet Development Kit (PDK), then most of this is already done for you. Going over all the details of using BoltSpec to test your plans is a little much for an email. So if you're interested in testing your plans, why not check out our new Testing Plans <https://puppet.com/docs/bolt/latest/testing_plans.html> documentation? VIEW THE DOCUMENTATION <https://puppet.com/docs/bolt/latest/testing_plans.html> [image: Tw] <https://twitter.com/puppetize> [image: Yt] <https://www.youtube.com/channel/UCPfMWIY-qNbLhIrbZm2BFMQ> [image: In] <https://www.linkedin.com/company/puppet/> *Bolt Documentation <https://puppet.com/docs/bolt/latest/bolt.html>* -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAK-b3DtJMw%3D9PP7-8TOELw4MRXh5y-zcaVBV5gmYavJvHu5Tmw%40mail.gmail.com.
