VERSION 2.24.0 *in this release*
✨ *new features* - Debugging Bolt commands just got easier, and no longer requires re-running a command with the --debug option. Bolt now automatically logs activity at the debug level to bolt-debug.log in the project directory. This log will be truncated each time Bolt is run. - Bolt's PowerShell cmdlets now provide parameter validation for the -LogLevel, -Rerun, and -Filter parameters. - Want to start using Bolt projects <https://puppet.com/docs/bolt/latest/projects.html> but already have an existing project directory structure? The bolt project migrate and Update-BoltProject commands have been updated to convert project directories to a Bolt project. We've also updated the command to automatically backup any files it modifies to a .bolt-bak directory in your project directory. Learn more about this command and its options in Bolt command reference <https://puppet.com/docs/bolt/latest/bolt_command_reference.html#project-migrate> . - You can quickly learn more about Bolt's concepts and features, and find links to the relevant documentation, using Bolt's new topic guides. To view a list of topic guides, run the bolt guide shell command or Get-Help about_bolt_* PowerShell cmdlet. Currently, Bolt ships with guides for the inventory and projects, with plans to add more in the future. Learn more about this new command and its options in Bolt command reference <https://puppet.com/docs/bolt/latest/bolt_command_reference.html#guide>. - Converting YAML plans to Puppet language plans will now preserve plan and parameter descriptions, ensuring that output for bolt plan show and Get-BoltPlan is consistent. You can read more about YAML plans in Writing plans in YAML <https://puppet.com/docs/bolt/latest/writing_yaml_plans.html>. 🔧 *bug fixes* - The PowerShell -Version parameter will now look at the RememberdInstallDir property for Bolt's version file location. - YAML plan parameters that do not have a default value will no longer display as optional in bolt plan show and Get-BoltPlan output. 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://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md> [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 Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAGdD-pVH9VNVZUZcpie30fyn83D-A7%3DpkLdpsT8%3D5-Y9PLDqPw%40mail.gmail.com.
