VERSION 3.10.0

*in this release*

✨  *new features*

   - You can now view which plugins are available to your project
using the bolt
   plugin show command and Get-BoltPlugin PowerShell cmdlet.
   - You can now look up values under Hiera's plan_hierarchy key from the
   CLI using the bolt lookup --plan-hierarchy command or Invoke-BoltLookup
   -PlanHierarchy PowerShell cmdlet. For more information, see the
   documentation
   <https://puppet.com/docs/bolt/latest/hiera.html#outside-apply-blocks-1>.

   - Need to interpolate variables into your Hiera lookups on the command
   line? You can now pass variables to the lookup command using
   variable=value syntax. For more information, see the documentation
   <https://puppet.com/docs/bolt/latest/hiera.html#outside-apply-blocks-1>.
   - Bolt packages on *nix platforms now ship with a bash autocompletion
   script. The script is saved to /etc/bash_completion.d/ when the Bolt
   package is installed.

🔧  *bug fixes*

   - BoltSpec now supports testing plans that invoke the parallelize() plan
   function. Previously, testing these plans caused Bolt to error.
   - The PuppetBolt PowerShell module now correctly passes remaining
   arguments to the -Arguments parameter for the
   Invoke-BoltScript cmdlet. Previously, the PowerShell parser would error
   if any remaining arguments were provided.

🚨  *deprecations*

   - The PuppetBolt PowerShell module will no longer ship with Bolt
   packages on Windows in a future release. The PuppetBolt PowerShell module
   can now be installed from the PowerShell Gallery
   <https://www.powershellgallery.com/packages/PuppetBolt> instead.


VIEW FULL RELEASE NOTES
<https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md#bolt-3100-2021-06-14>

*in the works*

   - Packages for macOS 11.
   - More readable type errors when running plans.
   - Support for waiting on all remaining backgrounded tasks using the
   wait() 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.

June's highlighted feature is: *streaming*!

*What is streaming?*

Don't worry, the Bolt team isn't releasing *yet another* streaming service.
When you run commands and scripts on targets, Bolt gives you the option of
streaming the output from these commands and scripts as they are executed
on the targets. This lets you see what is happening on every target you run
the action on in near real-time, making it easier to debug problems with
commands and scripts or to see where in the process of executing an action
the target is.


*How do I enable streaming?*

There are two ways to enable streaming in Bolt. You can either enable it
from the command line for a single run with the --stream command-line
option, or you can enable it permanently in your configuration with the
stream setting. Whenever Bolt streams output, it will print output from
stdout and stderr in the order it receives it from each target, and will
prepend each line with the name of the target that it came from.


To learn more about streaming, check out the documentation below!

VIEW THE DOCUMENTATION
<https://puppet.com/docs/bolt/latest/experimental_features.html#streaming-output>
[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-pUkgoHq0yhW9V4caysv9vA87_RVUCVmVKT78ubyfEdMjA%40mail.gmail.com.

Reply via email to