VERSION 2.25.0 *in this release*
✨ *new features* - The bundled puppet_agent module has a new puppet_agent::run plan which can be used to run the Puppet agent on a list of targets. This plan returns a set of results indicating whether the agent run was successful. If the Puppet agent was run, the result will include the detailed exit code and the run report. You can learn more about this plan on the Puppet Forge <https://forge.puppet.com/puppetlabs/puppet_agent>. 🔧 *bug fixes* - The BoltSpec library now initializes Bolt's custom logger. Previously, BoltSpec would error when it attempted to log messages to one of Bolt's custom log levels, such as trace. - Bolt's PowerShell module now correctly handles array parameters. Previously, array parameters would be automatically unwrapped, causing Bolt to raise an error. VIEW FULL RELEASE NOTES <https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md> *in the works* - Work continues on understanding the source of performance issues when running Bolt on Windows and macOS, and the different solutions we can implement to help improve performance. - Work continues on reworking our documentation to be clearer and more detailed. - Tasks will soon be able to return sensitive output. This will allow task authors to return data from a task that should not be logged or displayed on the CLI. - We have begun work on reducing the amount of time Bolt takes to install on Windows using the Bolt MSI. *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. August's highlighted feature is: *Bolt projects*! *What is a Bolt project?* A Bolt project is a directory that serves as the launching point for Bolt and allows you to create a shareable orchestration application that members of your team can quickly start using. Bolt projects contain all of the configuration and content relevant to your project, including the inventory file and content such as tasks and plans. *Why should I use a Bolt project?* Bolt projects make it easier to manage your Bolt project and can be utilized by other tools that use Bolt content. Additionally, Bolt projects enable several features that benefit both project authors and project consumers. - *Content allowlists* Project authors can specify an allowlist for both tasks and plans in their project's configuration, limiting which tasks and plans appear in the user interface. - *Project-level content* Project authors can quickly develop Bolt and Puppet content in the project directory without the need to create a module, speeding up the process of writing new tasks, plans, and manifests. - *Generate new plans *Projects enable the bolt plan new command, which will create a new plan in the project's plans directory. *How do I create a Bolt project?* To create a new Bolt project, all you need to do is create a file named bolt-project.yaml in your project directory and give your project a name by setting the name key in the file. You can also have Bolt create a Bolt project for you by running the bolt project init command in Unix shells or the New-BoltProject command in PowerShell. VIEW THE DOCUMENTATION <https://puppet.com/docs/bolt/latest/projects.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-pUenBkzYLNjukKC%2BW8AxoKhDqtkW0QZ4Z34TsNFd4ucog%40mail.gmail.com.
