VERSION 3.12.0

*in this release*

✨  *new features*

   - The puppet_agent::install task now supports installing the puppet-agent
   package on macOS 11 targets.
   - You can now silence warnings about exported resources not being
   supported in apply blocks by including the exported_resources ID under
   the disable-warnings configuration option. For more information about
   this setting, see the reference documentation
   
<https://puppet.com/docs/bolt/latest/bolt_project_reference.html#disable-warnings>
   .

🔧  *bug fixes*

   - Bolt no longer errors when showing plans or tasks when the plan or
   task cache includes a module that has been moved or deleted.


VIEW FULL RELEASE NOTES
<https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md>

*in the works*

   - A new plan function for printing messages in verbose mode.
   - New built-in plan functions for logging messages at Bolt's log levels.

   - Improvements to the wait() plan function.
   - Fedora 34 packages.

*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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUZS%2B_zBHO%2BqVRyWVPtjSYHUg8tBJ%3DOz3kYB_8YUD%2B6bA%40mail.gmail.com.

Reply via email to