in this release
This release includes breaking changes from the Bolt 2.x series. For more information about upgrading to the Bolt 3.x series, see the documentation.
|
✨ new features |
- Bolt packages and the Bolt gem now ship with Puppet 7.
- The Bolt PowerShell module, which ships with Windows packages, no longer includes the bolt PowerShell function. Instead, Bolt relies on a new batch file, bolt.bat, when executing commands.
- The module management workflow is now enabled by default, which means the default modulepath has been updated as well. The new default modulepath is ['modules'] instead of ['modules', 'site-modules', 'site']. Haven't used the new module management workflow yet? Check out the documentation for an overview.
- Have you ever run a Bolt task in PowerShell and gotten a cryptic message when it fails? We've updated the format for exceptions thrown in PowerShell to make it easier for users to understand why their task failed.
- Targets using the local transport now have the bundled-ruby configuration option set to true by default. This means local targets will use Bolt's Ruby and have the puppet-agent feature set by default. You can read more about this configuration option in the reference.
- Bolt now ships with the latest version of the puppetlabs/stdlib module, 6.6.0.
|
🔧 bug fixes |
- Warnings logged when a plan's documentation includes a parameter that is not in the plan signature now include the plan's name, making it easier to find the source of the warning.
|
🚨 removals |
- Bolt no longer supports the bolt.yaml configuration file. For project-level configuration, use bolt-project.yaml and inventory.yaml instead. For user- and system-level configuration, use
bolt-defaults.yaml instead. See the documentation for more information about these files. - We no longer ship Bolt packages for Debian 8.
- Bolt no longer supports puppet-agent versions earlier than 6.0.0. While applying Puppet code to targets with earlier versions of the puppet-agent package installed may still succeed, Bolt no longer guarantees compatibility.
- Bolt no longer supports PowerShell 2.0 on the controller or on targets. While running commands and tasks in PowerShell 2.0 may still succeed, Bolt no longer guarantees compatibility.
- Support for the --boltdir, --configfile, --debug,
--description, and --puppetfile command-line options has been removed. For a full list of supported command-line options, see the shell command and PowerShell cmdlet reference pages. - Support for the apply_settings, inventoryfile, plugin_hooks, and puppetfile configuration options has been removed. For a full list of supported configuration options, see the project and default configuration reference pages.
- Support for the notice log level has been removed. Use info instead. For more information about Bolt's log levels, see the documentation.
- The bolt puppetfile * commands and
*-BoltPuppetfile cmdlets have been removed. Use the
bolt module * commands and *-BoltModule cmdlets instead. For more information about these commands, see the module management overview. - The pkcs7 plugin no longer supports the private-key and
public-key parameters. Use the private_key and public_key parameters instead. You can find more information about this plugin on the Forge. - YAML plans no longer support the source or target step keys. Use upload and targets instead. For more information about supported plan step keys, see writing YAML plans.
- Bolt no longer ships with the aggregate::nodes plan. Use the aggregate::targets plan instead.
|
| VIEW FULL RELEASE NOTES |
| fd | | |
|
|
|
