VERSION 3.18.0 *in this release*
✨ *new features* - Bolt now respects the interpreters configuration option when running scripts, allowing you to specify a path to an interpreter. To enable this feature, set the future.script_interpreter option in your project configuration. For more information, see the bolt-project.yaml reference <https://puppet.com/docs/bolt/latest/bolt_project_reference.html#future>. - The bolt project init and New-BoltProject commands now create a .gitignore file with local Bolt files, simplifying the process of excluding user-specific files from your project repositories. - You can now provide an authorization token to the Forge when installing modules with Bolt using the new configuration option module-install.forge.authorization_token. For more information, see the documentation <https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#install-modules-using-an-authorization-token> . - Bolt now supports loading scripts from a project's or module's scripts/ directory by default when using a Puppet file reference ( <module>/scripts/<file>). For more information about this change, see the developer update <https://puppet.com/docs/bolt/latest/developer_updates.html#how-bolt-loads-scripts> . - Bolt now ships with the latest versions of each of its bundled modules, including: - package 2.1.0 <https://forge.puppet.com/puppetlabs/package/2.1.0/changelog> - puppet_agent 4.9.0 <https://forge.puppet.com/puppetlabs/puppet_agent/4.9.0/changelog> - puppet_conf 1.2.0 <https://forge.puppet.com/puppetlabs/puppet_conf/1.2.0/changelog> - reboot 4.1.0 <https://forge.puppet.com/puppetlabs/reboot/4.1.0/changelog> - service 2.1.0 <https://forge.puppet.com/puppetlabs/service/2.1.0/changelog> - stdlib 8.0.0 <https://forge.puppet.com/puppetlabs/stdlib/8.0.0/changelog> 🔧 *bug fixes* - Bolt now returns exit code 1 when an operation fails. Previously, Bolt returned exit code 2. - BoltSpec's allow_script, expect_script, allow_upload, and expect_upload functions now support absolute paths. Previously, only relative paths or Puppet file references were supported. - Bolt now correctly sets the main plan's ID during a plan run. Previously, Bolt was setting the main plan's ID incorrectly, causing Bolt to log some warnings when it should not have. - Bolt now supports using the scripts mount in Puppet manifests. Previously, the scripts mount was not supported. 🚨 *deprecations* - The future.file_paths configuration option is deprecated. Bolt no longer honors this setting and will look for scripts in a project's or module's scripts/ directory by default. VIEW FULL RELEASE NOTES <https://github.com/puppetlabs/bolt/blob/main/CHANGELOG.md#bolt-3180-2021-09-20> [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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAGdD-pWCOvy-OobqgwsYOWr-ukGdM6Xix7RdFBZU19oDnbkqyw%40mail.gmail.com.
