puppet-agent (8.10.0-2) unstable; urgency=medium

    Puppet documentation is now shipped separately in the new 'puppet-doc'
    package.

    This isn't a complete duplicate of what's available on the puppet.com
    website, but it includes key parts such as built-in function and type
    reference, as well as documentation about the core modules (eg. cron,
    sshkey, etc).

    An HTML index is available at /usr/share/doc/puppet/html/index.html

 -- Jérôme Charaoui <jerome@riseup.net>  Fri, 22 Nov 2024 17:39:59 -0500

puppet-agent (8.4.0-2) unstable; urgency=medium

    From this version on, Puppet in Debian will default to "reports = none".
    This will prevent unbounded growth of filesystem usage from report files,
    especially when using Puppet Server. This change affects both Puppet Server
    and "puppet apply".

    To revert to the previous default setting, set "reports = store" in
    the [main] section of puppet.conf.

 -- Jérôme Charaoui <jerome@riseup.net>  Thu, 05 Sep 2024 09:17:38 -0400

puppet-agent (8.4.0-1) unstable; urgency=medium

    Puppet 8 is a major new release that introduces some breaking changes from
    the previous version.

    Legacy facts, such as 'hostname', 'ipaddress', 'osfamily' and others, are
    now disabled by default. If your manifests refer to such facts, you're
    likely to encounter issues compiling or applying catalogs. The recommended
    action is to migrate to structured facts, eg. "$facts['os']['family']".
    Alternatively, setting 'include_legacy_facts=true' in puppet.conf may be
    used to re-enable legacy facts.

    In addition, strict mode catalog compilation is now enabled by default.
    This may be reverted by using the 'strict_variables=false' and
    'strict=warning' settings in puppet.conf.

    More information about upgrading from Puppet 7 to 8 can be found at:
    https://www.puppet.com/docs/puppet/8/upgrading-from-puppet7-to-puppet8.html

    Finally, for improved compatibility with the larger Puppet ecosystem, the
    package also now ships the same set of core modules as upstream, in the
    $vendormoduledir directory. The modules are: augeas_core, cron_core,
    host_core, mount_core, scheduled_task, selinux_core, sshkeys_core,
    yumrepo_core, zfs_core and zone_core.

 -- Jérôme Charaoui <jerome@riseup.net>  Mon, 19 Feb 2024 19:26:40 -0500
