VERSION 2.35.0

*in this release*

✨  *new features*

   - The new parallelize plan function brings additional parallelism
   capabilities to plans. This function accepts an array of input and a block,
   executes the block on each input, and returns a list of results that
   correspond to each input. To learn more about this new function and how to
   use it, see the documentation
   
<https://puppet.com/docs/bolt/latest/experimental_features.html#parallelize-function>
   .

   *This function is experimental.*
   - You can now filter tasks and plans available to your project in the
   project configuration file using shell-like glob patterns. This makes it
   easier to list multiple tasks and plans for your project without the need
   to list them all individually. Check out the documentation
   
<https://puppet.com/docs/bolt/latest/projects.html#limiting-displayed-plans-and-tasks>
to
   see how you can filter the tasks and plans that are available to your
   project.
   - Bolt now automatically sets a default port for connections to PuppetDB
   and Orchestrator, unless they are specified in configuration. The PuppetDB
   configuration option server_urls will set the default port to 8081,
   while the Orchestrator configuration option service-url will set the
   default port to 8143. To learn more about connecting to PuppetDB with Bolt,
   see the documentation
   <https://puppet.com/docs/bolt/latest/bolt_connect_puppetdb.html>. For
   more information about configuring the pcp transport for connecting to
   the Orchestrator, see the transport configuration reference
   <https://puppet.com/docs/bolt/latest/bolt_transports_reference.html#pcp>.

🔧  *bug fixes*

   - YAML plans that include an invalid plan step type will now result in a
   plan error. Previously, if a plan step was not a hash, Bolt would execute
   the plan normally.


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

*in the works*

   - You will soon be able to use an alternate Forge and use proxies when
   install modules using the bolt module add|install and
   Add|Install-BoltModule commands.
   - The new module management feature <https://pup.pt/bolt-modules> is
   soon moving out of experimental. Once this feature is considered stable,
   new projects created with bolt project init and New-BoltProject will
   automatically enable this feature.
   - Work is wrapping up on performance improvements on Windows.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
of what it is, why you might want to use it, and how it can be used in your
workflows.

November's highlighted feature is: *YAML plans*!

*What are YAML plans?*

Like plans written in the Puppet language, YAML plans allow you to define
workflows that include multiple tasks. However, YAML plans are much simpler
in structure and do not require learning the Puppet language. YAML plans
allow you to define a list of steps for Bolt to execute in order, such as
executing a command, running a task, or applying resources to a Target. You
can also define and use variables or evaluate Puppet code snippets as
needed. Because YAML plans are simpler to write, they're a great way to
quickly start defining workflows for your project.


*When should I use YAML plans?*

In general, if your plan only needs to define a simple workflow that does
not require sophisticated control flow or error handling, then a YAML plan
may be preferable to a Puppet language plan. YAML plans are simple to write
and don't require any knowledge of the Puppet language, so they're also
easier for users new to Bolt to understand.

But don't worry if you start writing a YAML plan only to find that you need
some features only available to Puppet language plans. Bolt has a built-in
command that makes converting YAML plans to Puppet language plans easy.
Simply run the bolt plan convert shell command or
Convert-BoltPlan PowerShell cmdlet to convert an existing YAML plan.


*How do I start writing a YAML plan?*

The first thing you'll want to do is check out the documentation on writing
plans in YAML <https://pup.pt/bolt-yaml-plans>. Once you know how to write
a YAML plan, you can create a new plan in a module or in your project's
plans directory. Bolt has a built-in command that you can use to quickly
create a new YAML plan with the basic structure of the plan filled out for
you.

To create a new plan with Bolt, run the bolt plan new shell command or the
New-BoltPlan PowerShell cmdlet. The command will create a new plan file in
the plans directory of your project.

Happy planning!

VIEW THE DOCUMENTATION <https://pup.pt/bolt-yaml-plans>
[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-pXM%3DAqFDr8B56nBeibDO0BT26qFP1-ppJ%2BBXZy-68mP3A%40mail.gmail.com.

Reply via email to