VERSION 2.44.0* *in this release*
**Due to an issue during the release process, Bolt 2.43.0 was not released.* ✨ *new features* - You can now mark individual plans as private to prevent them from appearing in bolt plan show and Get-BoltPlan output. Private plans can still be run directly from the command line and as sub-plans. Check out the documentation to see how to make Puppet language plans <https://puppet.com/docs/bolt/latest/writing_plans.html#making-plans-private> and YAML plans <https://puppet.com/docs/bolt/latest/writing_yaml_plans.html#private-key> private. - The PCP transport has a new read-timeout configuration option that lets you configure how long to wait for a response when making HTTP requests to the Orchestrator before timing out. Check out the transports reference <https://puppet.com/docs/bolt/latest/bolt_transports_reference.html#pcp> for a full list of configuration options. - The apply-settings configuration option now supports the log_level, trace, and evaltrace Puppet settings. Check out the configuration reference <https://puppet.com/docs/bolt/latest/bolt_project_reference.html#apply-settings> for a full list of supported Puppet settings. - Does your project include modules hosted in a repository other than a public GitHub repository? Do some of your modules not resolve correctly due to outdated metadata? You can now skip resolving dependencies for a module in your project configuration by setting the module's resolve key to false. For more information, see installing modules <https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#skip-dependency-resolution-for-a-module> . - Individual warnings can now be suppressed by setting the disable-warnings configuration option. This option accepts an array of IDs for warnings that should be suppressed. All warning messages logged by Bolt now include an ID at the end of the message. For more information, see the documentation <https://puppet.com/docs/bolt/latest/logs.html#suppress-warnings>. - Bolt's bundled modules have been updated to work with Puppet 7 on the Bolt controller. 🔧 *bug fixes* - Bolt's spinner has been updated to only run during plans when executing the run_*, file_upload, file_download, and wait_until_available plan functions. - Bolt now correctly shadows target and plan variables that collide with facts of the same name when running apply blocks. - Bolt will now pause execution of parallelize blocks when prompting the user for input. VIEW THE RELEASE NOTES <https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md#bolt-2440-2021-01-27> *in the works* - Work is wrapping up on Bolt 3.0, with plans to release the 3.0 gem and packages soon. - Work on improving performance on Windows has mostly wrapped up, with the improvements landing early in the 3.x series. *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. January's highlighted feature is: *module management*! *What is the module management feature?* Bolt can manage your project's module dependencies for you. By adding your project's direct dependencies to the project configuration file, Bolt will be able to resolve all transitive dependencies and version requirements, generate a Puppetfile, and install the modules. *Why should I have Bolt manage my project's modules?* Using the module management feature greatly simplifies the process of installing and adding new modules to your project. Instead of needing to locate all of a module's dependencies, find compatible versions for each module, and manually updating your Puppetfile, you can offload this work to Bolt. All you need to do is list the modules you care about in your project configuration file and Bolt will take care of the rest! *How do I start managing my project's modules with Bolt?* To have Bolt manage your project's module dependencies, you'll need to enable the feature by updating your project. We've made this process easy by updating the bolt project migrate command and Update-BoltProject Powershell cmdlet, which will guide you through the process of selecting which of your project's modules are direct dependencies and set up your project to use the new module management feature. *Can I still manage modules on my own?* Yes! Bolt still supports the legacy workflow of writing your own Puppetfile and installing modules without automatically resolving dependencies. Check out the documentation to learn how to manually manage a project's modules <https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#>. The module management feature includes several new Bolt commands, changes to Bolt's default configuration, and a few other changes as well. To get the most out of this feature, make sure to check out the documentation! VIEW THE DOCUMENTATION <https://puppet.com/docs/bolt/latest/modules.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-pX0qRGdx0083v4LTs5av%2Bh%3D6Lw6BHJzV4HaYmAcRRVwvA%40mail.gmail.com.
