1. Inventory was loaded for commands that didn't use it (1.20.0)
  2. YAML plan converter wrapped single-line evaluation steps (1.20.0)
  3. File upload stalled with local transport using run-as (1.18.0)
  4. Rerun file wasn't generated without an existing project directory (1.18.0)
  5. SELinux management didn't work on localhost (1.17.0)
  6. Linux implementation of the service and package tasks returned incorrect results (1.16.0)
  7. Remote tasks could run on non-remote targets (1.15.0)
  8. known_hosts weren't parsed correctly (1.15.0)
  9. Plan variables were visible to sub-plans (1.15.0)
  10. The _run_as option was clobbered by configuration (1.13.1)
  11. Tasks with certain configuration options failed when using stdin (1.13.1)
  12. Ruby task helper symbolized only top-level parameter keys (1.13.0)
  13. String segments in commands had to be triple-quoted in PowerShell (1.12.0)
  14. Unsecured download of the puppet_agent::install task (1.11.0)
  15. Unsecured download of the puppet_agent::install_powershell task (1.10.0)
  16. Bolt crashed if PuppetDB configuration was invalid (1.9.0)
  17. Local transport returned incorrect exit status (1.9.0)
  18. Standard library functions weren't packaged in 1.8.0 (1.8.1)
  19. puppet_agent::install task didn't match on Red Hat (1.8.0)
  20. Select module content missing from puppet-bolt package (1.7.0)
  21. wait_until_available function didn't work with Docker transport (1.6.0)
  22. Python task helper didn't generate appropriate errors (1.6.0)
  23. Plans with no return value weren't marked complete in PE (1.3.0)
  24. Some functions weren't available in the BoltSpec::Plans library (1.3.0)
  25. Task implementation not located relative to other files in installdir (1.2.0)
  26. Error when puppet_agent task not run as root (1.1.0)
  27. Bolt suppresses errors from transport (1.1.0)
  28. Loading bolt/executor is "breaking" gettext setup in spec tests (1.0.0)
  29. Deprecated functions in stdlib result in Evaluation Error (1.0.0)
  30. Bolt apply does not provide clientcert fact (1.0.0)
  31. C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional (1.0.0)

Security and bug fixes in the Bolt 1.x release series.

Inventory was loaded for commands that didn't use it (1.20.0)

Inventory was loaded even for commands that don't use targets, such as bolt task show. An error in the inventory could subsequently cause the command to fail. (BOLT-1268)

YAML plan converter wrapped single-line evaluation steps (1.20.0)

The bolt plan convert command wrapped single-line evaluation steps in a with() statement unnecessarily. (BOLT-1299)

File upload stalled with local transport using run-as (1.18.0)

The bolt file upload command stalled when using local the local transport if the destination file existed. (BOLT-1262)

Rerun file wasn't generated without an existing project directory (1.18.0)

If no Bolt project directory existed, a .rerun.json file wasn't created, preventing you from rerunning failed commands. Bolt now creates a default project directory when one doesn't exist so that .rerun.json files are generated as expected. (BOLT-1263)

SELinux management didn't work on localhost (1.17.0)

Bolt now ships with components similar to the Puppet agent to avoid discrepancies between using a puppet-agent to apply Puppet code locally versus using the Bolt puppet-agent. (BOLT-1244)

Linux implementation of the service and package tasks returned incorrect results (1.16.0)

The PowerShell and bash implementations for the service and package tasks are more robust and provide output more consistent with the Ruby implementation. (BOLT-1103, BOLT-1104)

Remote tasks could run on non-remote targets (1.15.0)

Remote tasks can now be run only on remote targets (BOLT-1203)

known_hosts weren't parsed correctly (1.15.0)

Previously, when a valid hostname entry was present in known_hosts and the host-key-check SSH configuration option was set, host key validation could fail when a valid IP address was not included in the known_hosts entry. This behavior was inconsistent with system SSH where the IP address is not required. Host key checking has been updated to match system SSH. (BOLT-495)

Plan variables were visible to sub-plans (1.15.0)

Variables defined in scope in a plan were visible to sub-plans called with run_plan. (BOLT-1190)

The _run_as option was clobbered by configuration (1.13.1)

The run-as configuration option took precedence over the _run_as parameter when calling run_* functions in a plan. The _run_as parameter now has a higher priority than config or CLI. (BOLT-1050)

Tasks with certain configuration options failed when using stdin (1.13.1)

When both interpreters and run-as were configured, tasks that required parameters to be passed over stdin failed. (BOLT-1155)

Ruby task helper symbolized only top-level parameter keys (1.13.0)

Previously the ruby_task_helperTaskHelper.run method symbolized only-top level parameter keys. Now nested keys are also symbolized. (BOLT-1053)

String segments in commands had to be triple-quoted in PowerShell (1.12.0)

When running Bolt in PowerShell with commands to be run on *nix nodes, string segments that could be interpreted by PowerShell needed to be triple-quoted. (BOLT-159)

Unsecured download of the puppet_agent::install task (1.11.0)

The bash implementation of the puppet_agent::install task now downloads packages over HTTPS instead of HTTP. This fix ensures the download is authenticated and secures against a man-in-the-middle attack.

Unsecured download of the puppet_agent::install_powershell task (1.10.0)

The PowerShell implementation of the puppet_agent::install task now downloads Windows .msi files using HTTPS instead of HTTP. This fix ensures the download is authenticated and secures against a man-in-the-middle attack.

Bolt crashed if PuppetDB configuration was invalid (1.9.0)

If an invalid puppetdb.conf file is detected, Bolt now issues a warning instead of crashing (BOLT-756)

Local transport returned incorrect exit status (1.9.0)

Local transport now correctly returns an exit code instead of the stat of the process status as an integer. (BOLT-1074)

Standard library functions weren't packaged in 1.8.0 (1.8.1)

Version 1.8.0 didn't include new standard library functions as intended. This release now includes standard library functions in the gem and packages. (BOLT-1065)

puppet_agent::install task didn't match on Red Hat (1.8.0)

The puppet_agent::install task now uses updates in the facts task to resolve Red Hat operating system facts and to download the correct puppet-agent package. (BOLT-997)

Select module content missing from puppet-bolt package (1.7.0)

Previous releases of the puppet-bolt package omitted the python_task_helper and ruby_task_helper modules. These are now included. (BOLT-1036)

wait_until_available function didn't work with Docker transport (1.6.0)

We merged the Docker transport and wait_until_available function in the same release, and they didn't play nicely together. (BOLT-1018)

Python task helper didn't generate appropriate errors (1.6.0)

The Python task helper included with Bolt didn't produce an error if an exception was thrown in a task implemented with the helper. (BOLT-1021)

Plans with no return value weren't marked complete in PE (1.3.0)

Bolt now correctly reports plan completion to PE for plans that don't return a value. Previously, a plan that didn't return a value incorrectly logged that the plan didn't complete. (BOLT-959)

Some functions weren't available in the BoltSpec::Plans library (1.3.0)

The BoltSpec::Plans library now supports plans that use without_default_logging and wait_until_available, and includes a setup helper that ensures tasks are found and that notice works. (BOLT-971)

Task implementation not located relative to other files in installdir (1.2.0)

When you use tasks that include shared code, the task executable is located alongside shared code at _installdir/MODULE/tasks/TASK. (BOLT-931)

Error when puppet_agent task not run as root (1.1.0)

The puppet_agent task now checks that it is run as root. When run as another user, it prints and fails with a helpful message. (BOLT-878)

Bolt suppresses errors from transport (1.1.0)

Previously, Bolt suppressed some exception errors thrown by transports. For example, when the ed25519 gem was not present for an Net::SSH process, the NotImplementedError for ed25519 keys would not appear. These errors are now identified and displayed. (BOLT-922)

Loading bolt/executor is "breaking" gettext setup in spec tests (1.0.0)

When Bolt is used as a library, it no longer loads code from r10k unless you explicitly require 'bolt/cli'.(BOLT-914)

Deprecated functions in stdlib result in Evaluation Error (1.0.0)

Manifest blocks will now allow use of deprecated functions from stdlib, and language features governed by the 'strict' setting in Puppet. (BOLT-900)

Bolt apply does not provide clientcert fact (1.0.0)

apply_prep has been updated to collect agent facts as listed in Puppet agent facts. (BOLT-898)

C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional (1.0.0)

When moving to Ruby 2.5, the .bat scripts in Bolt packaging reverted to hard-coded paths that were not accurate. As a result Bolt would be unusable outside of PowerShell. The .bat scripts have been fixed so they work from cmd.exe as well. (BOLT-886)

Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.