VERSION 2.42.0 *in this release*
✨ *new features* - Need to install modules hosted on an alternate Forge or configure a proxy? Bolt now supports the module-install configuration option when resolving module dependencies with the bolt module add|install commands and Add|Install-BoltModule cmdlets. For more information, see Install Forge modules from an alternate Forge <https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#install-forge-modules-from-an-alternate-forge> and Install modules using a proxy <https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#install-modules-using-a-proxy> . - Bolt now supports project-level plugins. Similar to module plugins, project-level plugins are implemented as project-level tasks. All types of plugins are supported at the project level. See the documentation for more information about writing plugins <https://puppet-docs-preview.netlify.app/docs/bolt/latest/writing_plugins.html#project-level-plugins> . - The following modules that are shipped with Bolt packages have been updated to their latest versions: - facts 1.3.0 - package 1.4.0 - puppet_agent 4.3.0 - puppet_conf 0.8.0 - reboot 3.1.0 - scheduled_task 2.3.1 - service 1.4.0 🔧 *bug fixes* - Inventory files now support top-level plugins, allowing you to use a plugin to set the entire inventory. Previously, only individual keys in the inventory supported plugins. - Bolt now automatically removes transport configuration keys that resolve to a nil value. Previously, Bolt would set these values as nil, which could cause Bolt to error. - YAML plans that contain a type or syntax error will no longer display a stack trace when converted to a Puppet plan using the bolt plan convert command or Convert-BoltPlan cmdlet. 🚨 *deprecations* - The puppetfile configuration option has been deprecated in favor of the module-install configuration option and will be removed in Bolt 3.0. - The bolt puppetfile * commands and *-BoltPuppetfile cmdlets have been deprecated in favor of the bolt module * commands and *-BoltModule commands and will be removed in Bolt 3.0. VIEW FULL RELEASE NOTES <https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md#bolt-2420-2021-01-11> *in the works* - Users will soon be able to designate plans as private. - Work continues on preparing for the Bolt 3.0 release. For more information about the changes planned, see the developer updates <https://puppet.com/docs/bolt/latest/developer_updates.html#changes-coming-in-bolt-30> . *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-pVqh359MgzGa-8viStb3kWoV5cWmHcDi9CTb%2BMeWguAeA%40mail.gmail.com.
