Bolt 3.0.1 is now available

[Puppet Product Updates]

VERSION 3.0.1 in this release 🔧  bug fixes Bolt now correctly installs a Puppetfile with bolt module install --no-resolve and Install-BoltModule -NoResolve even if the modules key is not configured or is an empty array. PowerShell users can now run Get-BoltVersion to list the Bolt version. This, and bolt --version should both load more quickly. VIEW FULL RELEASE NOTES in the works Look out for Windows Performance improvements coming soon!   We're working on a prototype for streaming output during remote execution. 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. February's highlighted feature is: Bolt plans! What is a Bolt plan? Bolt plans are Bolt's way of orchestrating complex workflows that can include running commands, scripts, Bolt tasks, and other logic. Plans allow users to run multiple tasks with one command, compute values for the input for a task, run certain tasks based on results of another task, and more. Bolt plans can be written in YAML or Puppet. When should I use a Bolt plan? Plans are useful when you find yourself wanting to compose multiple discreet steps together, for example running a command to install packages, then running a command to upload configuration files for those packages, then a task that starts the services those packages provide. Plans also let you compute inputs to steps in the plan, and Puppet plans have control flow logic that lets you determine whether to execute a step based on certain conditions. How do I create a Bolt plan? It's easiest to create a new plan inside a Bolt project. Have Bolt create a Bolt project for you by running the bolt project init myproject command in Unix shells or the New-BoltProject -Name myproject  command in PowerShell. Then run bolt plan new myproject in Unix shells or New-BoltPlan -Name myproject in PowerShell. VIEW THE DOCUMENTATION Bolt Documentation