Puppet release notes
These are the new features, resolved issues, and deprecations in this version of Puppet.
Puppet 8.2.0
Released August 2023.
Enhancements
macOS 13 support
Added support for macOS 13. PA-4772
Upgrade hiera-eyaml to 3.4+
Upgraded the hiera-eyaml component to 3.4. PA-5633
Add agent renew REST implementation
Added a method to send a client certificate renewal request to puppetserver. PUP-11854
Add Puppet setting to configure renewal interval
Added a setting for how often a node attempts to automatically renew its client certificate. PUP-11855
Retry failed CA & CRL refreshes sooner than the next interval
Puppet now attempts to refresh its CA and CRL sooner if initial attempts fail. PUP-11869
Send auto-renew attribute in CSR
Puppet now has an auto-renew attribute. If the agent supports auto-renewal, this attribute is added to the CSR (Certificate Signing Request) when it is generated and is used by Puppet Server to determine if auto-renewal TTL needs to be enabled for a given agent.
Agents that either do not have the hostcert_renewal_interval
setting or
have it set to 0 do not support auto-renewal and do not have
the auto-renew attribute. PUP-11896
Resolved issues
ffi and nokogiri gem use the wrong architecture when cross compiling
Fixed an issue where some gems would get built using the wrong architecture when cross compiling. PA-5666
certname with .pp
in the
middle doesn't pick up its own
manifest
Fixed an issue where manifests with .pp
in their file names were not
imported. PUP-11788
The --no-preprocess_deferred
option breaks deferring of Sensitive file
content
It is now possible to specify the content property for file
resources as containing a Deferred function that returns a
Sensitive value when lazily evaluating deferred values (the
default behavior in 8.x or when setting Puppet[:preprocess_deferred]
false in
7.x). For example: content =>
Deferred('new', [Sensitive, "password"])
.
PUP-11846
"Sleeping" agents raise "attempt to read body out of block (IOError)"
Previously, the agent erroneously tried to read a response body after closing the connection when a Puppet server requested the agent retry. Now when the agent is told to retry, the agent waits the specified sleep duration and does not error trying to read the request body after closing the connection. PUP-11853
puppet-resource_api bug with ruby 3.2 and integer munging
Updated puppet-resource_api to enable Ruby 3.2 compatibility. PA-5641
CRL authorityKeyIdentifier is not printed in Puppet 8
Fixed a regression in Puppet 8.x which caused the agent to omit the authorityKeyIdentifier extension for its CRL. PUP-11849
Security
Puppet 8.1.0
Released June 2023.
Enhancements
Refresh cached Puppet CA on Puppet client
Puppet agents will now attempt to
refresh their CA certificate(s) once per day. The frequency
is controlled by a new Puppet
setting: ca_refresh_interval
. PUP-10639
Resolved issues
Removed dependency on private class Concurrent::RubyThreadLocalVar
The Puppet::ThreadLocal
class no
longer relies on concurrent-ruby's private Concurrent::RubyThreadLocalVar
class and
instead uses Concurrent::ThreadLocalVar
. PUP-11723
Yumrepo target attribute does not work
Using the yumrepo
resource, enables
the target parameter to set the filepath for a Yum
repository to an arbitrary filepath or to an existing
repository file. Thank you to community member nabertrand for this
contribution. PA-5187
Security
Bump curl to 7.88.1
Upgraded the curl component from 7.86 to 7.88.1 to address several security vulnerabilities. PA-5393
Puppet 8.0.0
Released April 2023.
Enhancements
Freeze string literals
String literals are now immutable by default. PUP-11841
Strict mode enabled by default
For Puppet 8, strict mode is on by
default, meaning strict
defaults to error
and
strict_variables
defaults to true
. With
strict
set to
error, extra validation & checks are performed and fail
as an error. This change could be a breaking change if your
code does not conform to strict mode.
-
Accessing a variable without first defining it:
notice($myvar)
-
Accessing a legacy fact:
notice($facts['osfamily'])
-
Coercing a string into a numeric:
"1" + 1
To return to the previous behavior, set, strict
to warning
and strict_variables
to false
. PUP-11725
Change default value of exclude_unchanged_resources
Puppet reports no longer contain
detailed information about resources already matching their
desired state. Doing so reduces the amount of data stored in
PuppetDB in the
most common case when nothing has changed. The previous
behavior can be enabled by setting exclude_unchanged_resources=false
in
puppet.conf on each agent. PUP-11684
Drop Hiera 3 Requirement
Hiera 3 is no longer a hard dependency for Puppet. PUP-11621
Change default crl_refresh_interval
to 1 day
Puppet agent now defaults to refreshing its certificate revocation list (CRL) once every 24 hours. PUP-11602
Evaluate deferred functions lazily by default
Deferred functions follow normal resource relationships and
ordering, so it is now possible to install a dependency for
a deferred function and call the deferred function in a
single agent run. The previous behavior can be enabled by
setting preprocess_deferred=false
in puppet.conf
on each agent. PUP-11526
Exclude legacy facts by default
Legacy facts are no longer collected on Puppet agent or sent to Puppet server. This saves network bandwidth and reduces Puppetserver's memory footprint when using templates.
Since legacy facts are not available during compilation, they
cannot be referenced in Puppet code, ERB/EPP templates or Hiera configuration.
The legacy_facts
puppet-lint
plugin can help identify and automatically correct legacy
fact usage in Puppet code.
For more information visit https://github.com/puppetlabs/puppet-lint/blob/main/lib/puppet-lint/plugins/legacy_facts/legacy_facts.rb.
Legacy facts can be re-enabled by setting include_legacy_facts=true
in puppet.conf
on each agent. PUP-11430
Replace c_rehash
script with
native openssl implementation
Puppet agent 8 no longer bundles the
c_rehash
binary.
Instead, users must rely on the bundled openssl binary's
subcommand rehash. Example: /opt/puppetlabs/puppet/bin/openssl
rehash
. PA-4265
MRI Ruby 3.2
Puppet agent vendors Ruby 3.2. Ruby 3.2 has several notable breaking changes that may affect Puppet extensions, such as functions, custom facts, types & providers, report processors, etc. For a complete list visit: https://github.com/puppetlabs/puppet/wiki/Puppet-8-Compatibility#ruby-32-compatibility
If Puppet is installed as a gem, then it requires Ruby 3.1 or greater.
OpenSSL 3.0
Puppet agent vendors OpenSSL 3.0. If an application compiles against Puppet's openssl, then the application must be recompiled. For more information visit https://www.openssl.org/docs/man3.0/man7/migration_guide.html
Resolved issues
Deprecations and removals
Remove Windows ENV patches on Ruby 3
The Puppet::Util
methods for getting,
setting, clearing and merging environment variables are still available, but are
deprecated and will be removed in the next major release. Puppet 8 now uses Ruby's built-in ENV class to manage
environment variables on Windows. PUP-11348
Remove extra
cli option
The extra
CLI option, which was previously hidden,
has been entirely removed. PUP-11119
Drop openssl man pages and html docs
OpenSSL man pages and html docs are no longer included in Puppet agent. PA-4908
Drop Hiera 3 Component
This is a breaking change. The Hiera 3 gem is no longer vendored in puppet-agent packages, but may be installed separately.
If you rely on a Hiera 3 backend (a class that extends
Hiera::Backend
), you must convert your backend
to Hiera 5 using the steps found at https://www.puppet.com/docs/puppet/latest/hiera_migrate.html,
or manually install the Hiera 3 gem on all Puppet Server hosts. This change does not affect Hiera 5, puppet lookup or the hiera_include
, hiera_hash
, etc set of
functions. PA-4646
Drop PSON support
Support for the PSON (Pure JSON) serialization format has been removed. Puppet agents may fail if binary data is accidentally
added to the catalog without using the Binary
data
type or binary_file
function. For more information
visit https://www.puppet.com/docs/puppet/latest/lang_data_binary.html.
It is possible, but not recommended, to reenable PSON support by installing the
puppet-pson gem on all agents and server hosts and setting preferred_serialization_format=pson
in puppet.conf on each agent.