| The next release in the Puppet 6 series, Puppet 6.20.0, is now available! The release contains bug fixes and minor improvements, including: New features JSON terminus for node and report This release implements JSON termini for node and report indirection. The format of the last_run_report.yaml report can be affected by the cache setting key of the report terminus in the routes.yaml file. To ensure the file extension matches the content, update the lastrunreport configuration to reflect the terminus changes (lastrunreport = $statedir/last_run_report.json). PUP-10712 JSON terminus for facts This release adds a new JSON terminus for facts, allowing them to be stored and loaded as JSON. Puppet agents continue to default to YAML, but you can use JSON by configuring the agent application in routes.yaml. Puppet Server 7 also caches facts as JSON instead of YAML by default. You can re-enable the old YAML terminus in routes.yaml. PUP-10656 Multiple logdest locations in puppet.conf accepted You can set multiple logdest locations using a comma separated list. For example: /path/file1,console,/path/file2. PUP-10795 New serverport setting type The serverport setting is an alias for masterport. PUP-10725 The puppet module install command lists unsatisfiable dependencies If the puppet module install command fails, Puppet returns a more detailed error, including the unsatisfiable module(s) and its ranges. PUP-9176 Interpolation of sensitive values in EPP templates Previously, if you interpolated a sensitive value in a template, you were required to unwrap the sensitive value and rewrap the result. Now the epp and inline_epp functions automatically return a Sensitive value if any interpolated variables are sensitive. For example: inline_epp("Password is <%= Sensitive('opensesame') %>"). Note that these changes just apply to EPP templates, not ERB templates. PUP-8969 OpenSSL bumped to 1.1.1i This release bumps OpenSSL to 1.1.1i. PA-3513 Curl bumped to 7.74.0 This release bumps Curl to 7.74.0. PA-3512 (Experimental feature) puppet facts diff action This release adds a new action called puppet facts diff to check if there are differences between Facter 3 and Facter 4 outputs. Facts that change over time like memory and uptime are ignored. PUP-10815 Deprecations func3x_check setting removed The func3x_check setting has been removed. PUP-10724 Resolved issues The puppet apply command creates warnings This release eliminates Ruby 2.7.x warnings when running puppet apply with node statements. PUP-10845 Remove Pathname#cleanpath workaround This release removes an unnecessary workaround when cleaning file paths, as Ruby 1.9 is no longer supported. PUP-10840 Cached catalog contains the result of deferred evaluation instead of the deferred function Puppet 6.12.0 introduced a regression that caused the result of a deferred function to be stored in the cached catalog. As a result, an agent running with a cached catalog would not re-evaluate the deferred function. This is now fixed. PUP-10818 Calling scope#tags results in undefined method Previously, calling the tags method within an ERB template resulted in a confusing error message. The error message now makes it clear that this method is not supported. PUP-10779 Puppet agent installation fails when msgpack is enabled on puppetserver Previously, the agent failed to deserialize the catalog and fail the run if the msgpack gem was enabled but not installed. Now the agent only supports that format when the msgpack gem is installed in the agents vendored Ruby. PUP-10772 Setting facterng twice raises an exception Previously, calling puppet config set facterng true twice resulted in a failure. This is now fixed and facterng is only enabled if it is not already. PUP-10731 Puppet feature detection leaves Ruby gems in a bad state This release fixes a Ruby gem caching issue that prevented the agent from applying a catalog if a gem was managed using the native package manager, such as yum or apt. PUP-10719 Fine grained environment timeout issues Previously, if the environment.conf for an environment was updated and the environment was cleared, puppetserver used old values for per-environment settings. This happened if the environment timed out or if the environment was explicitly cleared using puppetserver's environment cache REST API. With this fix, if an environment is cleared, Puppet reloads the per-environment settings from the updated environment.conf. PUP-10713. Setting certname in multiple sections bypasses validation Previously, Puppet only validated the certname setting when specified in the main setting, but not if the value was in a non-global setting like agent. As a result, it was possible to set the certname setting to a value containing uppercase letters and prevent the agent from obtaining a certificate the next time it ran. Puppet now validates the certname setting regardless of which setting the value is specified in. PUP-9481 puppet config set certname accepts upper-case names Previously, the puppet config set command could set a value that was invalid, causing Puppet to fail the next time it ran or the service was restarted. Now the command validates the value before committing the change to puppet.conf. PUP-2173 3x functions cannot be called from deferred functions in Puppet agent This release allows deferred 3.x functions, like sprintf, to be called during a Puppet agent run. PUP-10819 Issue with Puppet creating production folder when multiple environment paths are set Previously, the production environment folder was automatically created at every Puppet ran in the first search path, if it did not already exist. This release Puppet Puppet searches all the given paths before creating a new production environment folder. PUP-10842 Facter 3.14.15 Released 20 January 2020 and shipped with Puppet Platform 6.20.0. This release includes minor maintenance changes. For the latest features, see the release notes for Facter 3.14.14. Puppet Server 6.15.0 Released 20 January 2021 The puppetserver CA CLI now provides a migrate command to move the CA directory from the Puppet confdir to the puppetserver confdir. It leaves behind a symlink on the old CA location, pointing to the new location at /etc/puppetlabs/puppetserver/ca. The symlink provides backwards compatibility for tools still expecting the cadir to exist in the old location. In a future release, the cadir setting will be removed entirely. SERVER-2896 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html |
