[Puppet Users] Puppet DevX Releases

['Puppet Product Updates' via Puppet Users]

Puppet DevX Releases

*DevX tools*
You will notice the title of these updates change as our tooling team is
renamed to DevX to be clear on our focus on the developer experience
with our tooling.

Another change that is taking place is to ensure we have clear ownership
and consistent contributor processes for the ruby gems puppet-lint and
rspec-puppet. They will soon be republished into a new namespace and while
we appreciate there will be some concern around this we will work hard to
review and create PRs on visible community dependencies and raise awareness
of the change. We also would highlight we greatly appreciate Rodjek (Tim)
authorship and contributions to these projects.

Puppet-vscode also received its first release in two years. We are focused
on minor fixes for now but this has re-established our release process and
you should expect to see a much more regular release cycle from now on.

*Development tools released:*

   - ruby-pwsh  (1.0.0)


   - dependency_checker  (
   1.0.1)
   - puppet_litmus  (1.1.3)
   - puppet-vscode
   
(1.4.2)
   - puppet-lint  (4.2.1)
   - puppetlabs_spec_helper
    (6.0.3)
   - rspec-puppet  (4.0.0)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nEu3ccDSj5s_cMQbjsq8uZNnTpaCvVQUnMmkGDuW1Ofgw%40mail.gmail.com.

[Puppet Users] Re: Puppet Content Releases

['Puppet Product Updates' via Puppet Users]

Puppet Content Releases*Supported modules*
<https://hackmd.io/@ppt-iac/ByG1Lpegn#Supported-modules>An important
clarification was brought to my attention, thanks bastelfreak (Tim), that
the postgresql module was updated to 10.0.1 and that the
previously mentioned 10.0.0 version should NOT be used.


*Supported modules released:·puppetlabs-postgresql
<https://github.com/puppetlabs/puppetlabs-postgresql> (10.0.1)*


On Tue, Oct 17, 2023 at 3:42 PM Puppet Product Updates <
puppet-product-upda...@puppet.com> wrote:

> Puppet Content Releases
> <https://hackmd.io/@ppt-iac/ByG1Lpegn#Supported-modules>
> *Supported modules*
> Some great development work has taken place including completing the
> conversion of templates from ERB to EPP, the firewall module getting
> restructured to use Puppet resource API, strict types and clean up of
> parameters and some major work took place on the apache module to meet
> community requests and modernise.
>
> It is also important to note all DSC autogenerated modules were downgraded
> from supported to approved to reflect the fact our process does not support
> the content taken from the Powershell Gallery but only the process that
> wraps them.
>
>
>
> *Supported modules released:·puppetlabs-postgresql
> <https://github.com/puppetlabs/puppetlabs-postgresql> (10.0.0)·
> puppetlabs-stdlib <https://github.com/puppetlabs/puppetlabs-stdlib> (9.4.0)
> ·puppetlabs-apache
> <https://github.com/puppetlabs/puppetlabs-apache> (11.1.0) ·
> puppetlabs-haproxy
> <https://github.com/puppetlabs/puppetlabs-haproxy> (7.2.1) ·
> puppetlabs_spec_helper
> <https://rubygems.org/gems/puppetlabs_spec_helper> (6.0.2) ·
> puppetlabs-firewall
> <http://github.com/puppetlabs/puppetlabs-firewall> (7.0.1)·
> puppetlabs-apache
> <https://github.com/puppetlabs/puppetlabs-apache> (11.0.0)*
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nEfc_DhWDOFAGyGf-OanOBCzyu9mt7D91_OyrgxaEv0ag%40mail.gmail.com.

[Puppet Users] Puppet Content Releases

['Puppet Product Updates' via Puppet Users]

Puppet Content Releases

*Supported modules*
Some great development work has taken place including completing the
conversion of templates from ERB to EPP, the firewall module getting
restructured to use Puppet resource API, strict types and clean up of
parameters and some major work took place on the apache module to meet
community requests and modernise.

It is also important to note all DSC autogenerated modules were downgraded
from supported to approved to reflect the fact our process does not support
the content taken from the Powershell Gallery but only the process that
wraps them.



*Supported modules released:·puppetlabs-postgresql
 (10.0.0)·
puppetlabs-stdlib  (9.4.0)
·puppetlabs-apache
 (11.1.0) ·
puppetlabs-haproxy
 (7.2.1) ·
puppetlabs_spec_helper
 (6.0.2) ·
puppetlabs-firewall
 (7.0.1)·
puppetlabs-apache
 (11.0.0)*

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nG3Q9o7jds1gHuKdke2aK47BMhoNTQJce8zuP6W-Pj1xQ%40mail.gmail.com.

[Puppet Users] Puppet Tooling Releases

['Puppet Product Updates' via Puppet Users]

Puppet Tooling Releases

*Development tools*
You will notice the title of these updates change as we move to having
dedicated teams for tooling and content separately. This is also reflected
in codeowners files in the repos where you will now see tooling and modules
for each team respectively.

The main work taking place is for the newly dedicated tooling team to fully
familiarise themselves with the development toolset and a new  plugin has
been added into puppet-lint, the  check_unsafe_interpolations plugin. This
helps Puppet developers to check their Puppet code for interpolated
variables that could be vulnerable to code injection attacks

*Development tools released:*

   - ruby-pwsh  (1.0.0)


   - dependency_checker  (
   1.0.1)
   - puppet_litmus  (1.1.3)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nHKno7qQv6dbpwMWAPPg5CCtAUuMXFBDwCPZb-kFUDVWg%40mail.gmail.com.

[Puppet Users] Puppet Content releases

['Puppet Product Updates' via Puppet Users]

Puppet Content Releases
Supported modulesYou
will notice the title of these updates change as we move to having
dedicated teams for tooling and content separately. This is also reflected
in codeowners files in the repos where you will now see tooling and modules
for each team respectively.

The main work taking place for content is work to convert ERB files to EPP
on our modules and work going into the CI pipelines to help us
deliver change faster.  Additionally, the Firewall module is being changed
to utilise the resource_api.

*Supported modules released:*
- puppetlabs-haproxy  (
7.2.0)
- puppetlabs-stdlib  (9.3.0
)
- puppetlabs-java  (10.1.2)
- puppetlabs-firewall  (
6.0.0)
- puppetlabs-docker  (9.1.0
)
- ComputerManagementDsc
 (
9.0.0)
- puppetlabs-lvm  (2.0.3)

*Unsupported modules donated to Puppet from VOX:*
- puppetlabs-windows_env

- puppetlabs-sslcertificate

- puppetlabs-windows_eventlog


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nEGZMzi1fWyZGex-gpYq8wLcd9LAm4FFXGzOEJKQw-CKw%40mail.gmail.com.

[Puppet Users] Learning VM repos archived and moved to toy chest

['Puppet Product Updates' via Puppet Users]

The Puppet Learning VM is a fond memory of most long term Puppet users. It
was often one of the first interactions with Puppet and after some
inevitable fumbling with VirtualBox or corporate laptop issues gave a fun
and focused way to learn Puppet via the various quests.As technology has
moved on and public cloud made provisioning even easier Puppet practice
labs using instruqt is now well established and available seamlessly via
your browsers from https://training.puppet.com/Therefore the repositories
related to the Puppet learning VM have been put into the toy chest.-
https://github.com/puppetlabs/puppet-quest-guide
- https://github.com/puppetlabs/quest
- https://github.com/puppetlabs/pltraining-learning
- https://github.com/puppetlabs/pltraining-bootstrapIf any community
member/group wishes to adopt these projects they can get in contact.As we
say a fond farewell to the learning VM, you can find out more about the
practice labs which are free and accessible at any time.-
https://www.puppet.com/blog/puppet-practice-labs
- https://instruqt.com/blog/frictionless-hands-on-customer-education
-
https://support.puppet.com/hc/en-us/articles/4404442556567-Puppet-Practice-Labs-Free-browser-based-hands-on-learning

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nE_rHHkzQYw0nKL4h5novrjeMJ2WUXVCb3c_D6B_LZUdA%40mail.gmail.com.

[Puppet Users] Puppet Content and Tooling Releases

['Puppet Product Updates' via Puppet Users]

Puppet Content and Tooling Releases
Supported modulesThe
main work you will see going on right now is to ensure modules are
compatible with stdlib 9.x

*Supported modules released:*
- puppetlabs-docker 
 (9.0.1)
- puppetlabs-java  (10.1.1)
- puppetlabs-apache 
 (10.1.1)
- puppetlabs-sqlserver 
 (4.1.0)
- puppetlabs-apache 
 (10.1.1)
- puppetlabs-ntp  (10.1.0)
- puppetlabs-inifile 
 (6.1.0)
- puppetlabs-mysql  (15.0.0)
- puppetlabs-motd  (7.1.0)
- puppetlabs-registry 
 (5.0.1)
- puppetlabs-accounts 
 (8.1.0)
- puppetlabs-wsus_client
 (6.1.0)
- puppetlabs-stdlib 
 (9.2.0)
- puppetlabs-concat 
 (9.0.0)
- puppetlabs-vcsrepo 
 (6.1.0)
- puppetlabs-postgresql
 (9.1.0)
- puppetlabs-kubernetes
 (8.0.0)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nE7UCcuMLm5A7kAQyY1raJ%3DD3J-BML1Bvy6XARiiNWfew%40mail.gmail.com.

[Puppet Users] PDK 3.0.0 released

['Puppet Product Updates' via Puppet Users]

*Puppet Content and Tooling Releases*

*Development tools*

*PDK 3.0.0*

The Puppet Development toolkit (PDK) provides integrated testing tools and
a command line interface to help you develop, validate, and test modules.

* PDK 3.0.0 is a backward incompatible release.*


*How to install it:*

Manual: https://www.puppet.com/downloads/puppet-development-kit
brew: brew install pdk
winget: winget install pdk
choclatey: choco install pdk
docker: docker pull puppet/pdk:3.0.0.0

*Key features/changes:*

·  Ruby 3.2.2 is now the default version of Ruby.

·  Puppet 8 is now the default version of Puppet.

·  PDK no longer relies on PowerShell, you are able to use PDK from any
terminal that honours your PATH variable.

·  As of this release, PDK now only includes the latest supported
Puppet versions at the time of build.

·   The --pe-version flag has been deprecated

Full release notes


*Feedback*

- https://github.com/puppetlabs/pdk/issues
- https://github.com/puppetlabs/pdk-templates/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nHHU9-y8t8BCnem0vJDKjGTDqF3-JFMxrgkMv-%3D4mkYtg%40mail.gmail.com.

[Puppet Users] Puppet Content and Tooling Releases

['Puppet Product Updates' via Puppet Users]

Puppet Content and Tooling Releases
Supported modulesPuppet
8 support was completed with the Kubernetes module release and further
deferred functions were added to modules. As one of the most used and
requested modules for supported status LVM was updated to be a supported
module.

*Supported modules added:*
puppetlabs-lvm
 (2.0.2)

*Supported modules released:*

puppetlabs-kubernetes
 (8.0.0)
puppetlabs-tomcat 
(7.1.0)
puppetlabs-chocolatey
 (8.0.0)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nGo2UKui-Xt8RorZzaWycYVW5hTW5dgbMcMRnv9mqAHGg%40mail.gmail.com.

[Puppet Users] Puppet Spoke 1.1.1 recertified to Utah

['Puppet Product Updates' via Puppet Users]

*Puppet Integration Releases - *

*ServiceNow*

Puppet Spoke 1.1.1


Puppet Spoke gives I&O and DevOps teams self-service workflows to use for
managing Puppet assets directly from ServiceNow's CMBD interface. You get
the power of Puppet's data and action engine without leaving ServiceNow.

*Key features/changes:*
·  Certified to ServiceNow Utah*Support Contact*

Puppet Integrations Engineering

team-...@puppet.com
*Find out more*https://www.puppet.com/integrations/servicenow

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nHn5UEAQD8gQb8tN-DvherwsQNKQ87zo0kOzOOFUnZsvA%40mail.gmail.com.

[Puppet Users] Fwd: Puppet Content and Tooling Releases

['Puppet Product Updates' via Puppet Users]

Puppet Content and Tooling Releases
Supported modulesAfter
a small break in module release announcements with conferences, we are now
reaching the end of Puppet 8 module updates with only the Kubernetes module
awaiting an update.*Supported modules released:*


* - puppetlabs-vcsrepo  (6.0.1)-
puppetlabs-java_ks  (5.0.0)-
puppetlabs-concat  (8.0.1)-
puppetlabs-postgresql  (9.0.3)-
puppetlabs-docker
 (7.0.0)-
puppetlabs-postgresql  (9.0.2)-
puppetlabs-stdlib  (9.0.0)-
puppetlabs-powershell
 (6.0.0)-
puppetlabs-apache
 (10.0.0)-
puppetlabs-reboot  (5.0.0)-
puppetlabs-sqlserver  (4.0.0)-
puppetlabs-puppet_conf
(2.0.0)-
puppetlabs-influxdb  (2.1.0)-
puppetlabs-kubernetes
 (7.1.1)*

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nG91KTy2YmUN9sk_sdD%2Bs6vVS9B6mwuUDdxosj%3DmQpCvw%40mail.gmail.com.

[Puppet Users] Service Graph Connector for Puppet 1.2.1 released

['Puppet Product Updates' via Puppet Users]

*Puppet Integration Releases*

*ServiceNow*

Service Graph Connector for Puppet 1.2.1


The Service Graph Connector for Puppet ingests data from multiple Puppet
Enterprises directly into ServiceNow’s CMDB to give you and your team rich,
relevant data to make informed decisions across your on-prem and cloud
infrastructure. Increase the data share frequency and wealth of information
on each resource in the form of Facts, collected by the Puppet Agent and
shared directly into the ServiceNow CMDB for real-time data advantage.

*Key features/changes:*


   - Certified to ServiceNow Utah
   - Any node that does not contain the configured Unique Attribute on the
   Fact Configurations page will be ingored and not imported.
   - The Puppet Connector has moved in the Menu to be included in Service
   Graph Connectors

*Support Contact*

Puppet Integrations Engineering

team-...@puppet.com
*Find out more*https://www.puppet.com/integrations/servicenow

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nGMOufYZAfLAf%3DgKj%2BXMnzvjTgKp%2BYL1ypcSgnRjLekNw%40mail.gmail.com.

[Puppet Users] Puppet Content and Tooling Releases

[Puppet Product Updates]

Puppet Content and Tooling Releases
Supported modules

puppetlabs-concat  v8.0.0

The concat module lets you gather concat::fragment resources from your
other modules and order them into a coherent file through a single concat
 resource.
Key
features/changes:
Added

   - Add Support for Puppet 8 / Drop Support for Puppet 6





Full changelog v7.4.0 to v8.0.0


Feedback

https://github.com/puppetlabs/concat/issues

puppetlabs-inifile  v6.0.0

Many applications use INI-style configuration files to store their
settings. This module supplies two custom resource types to let you manage
those settings through Puppet.


Key features/changes Added

   - Add Support for Puppet 8 / Drop Support for Puppet 6

Full changelog v5.4.1 to v6.0.0

Feedback

https://github.com/puppetlabs/inifile/issues
puppetlabs-mysql  v14.0.0

The mysql module installs, configures, and manages the MySQL service.

This module manages both the installation and configuration of MySQL, as
well as extending Puppet to allow management of MySQL resources, such as
databases, users, and grants.
Key
features/changes Added

   - Add Support for Puppet 8 / Drop Support for Puppet 6


Full changelog v13.3.0 to v14.0.0

Feedback

https://github.com/puppetlabs/mysql/issues

puppetlabs-vcsrepo  v6.0.0

The vcsrepo module provides a single type with providers to support various
version control systems:



Key features/changes Added

   - Add Support for Puppet 8 / Drop Support for Puppet 6


Full changelog v5.5.0 to v6.0.0

Feedback

https://github.com/puppetlabs/puppetlabs-vcsrepo/issues

puppetlabs-java  v10.0.0

The java module can automatically install Java jdk or jre on a wide variety
of systems. Java is a base component for many software platforms, but Java
system packages don't always follow packaging conventions. The java module
simplifies the Java installation process.


Key
features/changes Added

   - Add Support for Puppet 8 / Drop Support for Puppet 6


Full Changelog v9.0.1 to v10.0.0

Feedback

https://github.com/puppetlabs/puppetlabs-java/issues

puppetlabs-java_ks  v4.4.2

The java_ks module contains a type called java_ks and a single provider
named keytool. Their purpose is to enable importation of arbitrary, already
generated and signed certificates into a Java keystore for use by various
applications.


Key features/changes Added

   - Params parameter documented and set to a type


Full changelog v4.4.1 to v4.4.2

Feedback

https://github.com/puppetlabs/puppetlabs-java_ks/issues


puppetlabs-tomcat  v7.0.0

Tomcat is a Java web service provider. The tomcat module lets you use
Puppet to install Tomcat, manage its configuration file, and deploy web
apps to it. It supports multiple instances of Tomcat spanning multiple
versions.
Key
features/changes Added

   -
   - Add Support for Puppet 8 / Drop Support for Puppet 6


Full changelog v6.4.1 to v7.0.0

Feedback

https://github.com/puppetlabs/puppetlabs-tomcat/issues


puppetlabs-acl  v5.0.0

The acl module lets you use Puppet to manage Access Control Lists (ACLs) on
Windows.

Windows uses Access Control Lists (ACLs) to store permissions information.
An ACL is typically 

[Puppet Users] Content and tooling - PDK future and depreciation of PCT and PRM

[Puppet Product Updates]

Puppet Content and Tooling Releases
Tooling
We have chosen to continue to build on PDK as the future direction of
Puppets developer tooling and to archive Puppet Content Templates (PCT) and
Puppet Runtime Manager (PRM).
These projects provided valuable lessons which will be fed into PDK 3.x

The full details of this approach can be found discussed in the blog
https://www.puppet.com/blog/faq-puppet-developer-kit-pdk

If any part of the community wants to adopt these projects for their own
use please let us know.
Puppet Content Templates (PCT) - *Archived *and moved to
https://github.com/puppetlabs-toy-chest/pct
Puppet Runtime Manager (PRM)   *Archived *and moved to
https://github.com/puppetlabs-toy-chest/prm

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nE3ePE8MS23kmOWDizHjj_i0uE-25smp05NhTAq-KcqWA%40mail.gmail.com.

[Puppet Users] Puppet Content and Tooling Releases

[Puppet Product Updates]

Puppet Product Updates 
Thu, Apr 13, 12:28 AM (6 days ago)
to bcc: puppet-users, bcc: voxpupuli, bcc: puppet-dev, bcc: [Internal]
Puppet Content and Tooling Releases
<https://hackmd.io/@ppt-iac/ByG1Lpegn#Supported-modules>Tooling
As part of ongoing work to prepare for the release of Puppet 8 development
tools are being updated to support ruby 3 and Puppet 8 while ending support
of Puppet 6.


   - puppet_litmus *v1.0.0-rc.1* (release notes
   <https://github.com/puppetlabs/puppet_litmus/releases/tag/v1.0.0.rc.1>)
   - puppetlabs_spec_helper *v6.0.0-rc.1* (release notes
   
<https://github.com/puppetlabs/puppetlabs_spec_helper/releases/tag/v6.0.0.rc.1>
   )
   - puppet-modulebuilder *v1.0.0-rc.1* (release notes
   <https://github.com/puppetlabs/puppet-modulebuilder/releases/tag/v1.0.0.rc.1>
   )
   - rspec-puppet *v3.0.0-rc.1 *(release notes
   <https://github.com/puppetlabs/rspec-puppet/releases/tag/v3.0.0.rc.1>)
   - puppet-lint *v4.0.0-rc.1 *(release notes
   <https://github.com/puppetlabs/puppet-lint/releases/tag/v4.0.0.rc.1>)
   - puppet_litmus *v1.0.0.-rc.1* (release notes
   <https://github.com/puppetlabs/puppet_litmus/releases/tag/v1.0.0.rc.1>)
   - dependency_checker *v1.0.0-rc.1 *(release notes
   <https://github.com/puppetlabs/dependency_checker/releases/tag/v1.0.0.rc.1>
   )
   - puppet-strings *v4.0.0-rc.1* (release notes
   <https://github.com/puppetlabs/puppet-strings/releases/tag/v4.0.0.rc.1>)
   - ruby-pwsh *v0.11.0-rc.1* (release notes
   <https://github.com/puppetlabs/ruby-pwsh/releases/tag/v0.11.0.rc.1>)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nFBOhZe5cDLDon4yVQ3AxdE%2B6PT4%3DBJCbC4k-j6QJK%2BUQ%40mail.gmail.com.

[Puppet Users] Splunk_hec 1.4.0 released

[Puppet Product Updates]

*Puppet Integration Releases*

*Splunk*

Splunk_hec 1.4.0 
 released

This module provides three services to Puppet and Splunk users.


   - A report processor to allow sending Puppet Agent run reports to Splunk
   - A fact terminus to submit node facts to Splunk
   - A PE Event Forwarding processor

Key features/changes:
Fixed

   - Event filtering for pe-console and code-manager events are no longer
   ignored





Full changelog v1.3.0 to v1.4.0


Feedback

https://github.com/puppetlabs/puppetlabs-splunk_hec/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nH9kiFKJHn4acu0jrF%2BO0JHurT-8VpAh0UPDcd%2BCJH9ag%40mail.gmail.com.

[Puppet Users] Puppet Spoke 1.1.1 release

[Puppet Product Updates]

*Puppet Integration Releases*

*ServiceNow*

Puppet Spoke 1.1.1


Puppet Spoke gives I&O and DevOps teams self-service workflows to use for
managing Puppet assets directly from ServiceNow's CMBD interface. You get
the power of Puppet's data and action engine without leaving ServiceNow.

*Key features/changes:*
·  Certified to ServiceNow Tokyo*Support Contact*

Puppet Integrations Engineering

team-...@puppet.com
*Find out more*https://www.puppet.com/integrations/servicenow

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nGkpa13vSFo-9kKinJHQZAJAcs-KZ64RN6paAssrufcNw%40mail.gmail.com.

[Puppet Users] PDK 2.7.1 released

[Puppet Product Updates]

 Puppet Content and Tooling Releases Development tools
*PDK 2.7.1* The Puppet Development toolkit (PDK) provides integrated
testing tools and a command line interface to help you develop, validate,
and test modules

*Where you can find it:*
- https://www.puppet.com/downloads/puppet-development-kit
- https://community.chocolatey.org/packages/pdk/2.7.1.0
 *Key
features/changes:*

·  PDK Templates have been updated to 2.7.4

·  Fixes an issue with duplicate build-ids for RedHat 9 packages

Full release notes 
*Feedback*

- https://github.com/puppetlabs/pdk/issues
- https://github.com/puppetlabs/pdk-templates/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nFnGJ2y5Jw%3DBJvZnRjk%3DJUkmygM_cQr6tBPkPnhJLYbfA%40mail.gmail.com.

[Puppet Users] Service Graph Connector for Puppet 1.2.0 released

[Puppet Product Updates]

*Puppet Integration Releases*

*ServiceNow*

Service Graph Connector for Puppet 1.2.0


The Service Graph Connector for Puppet ingests data from multiple Puppet
Enterprises directly into ServiceNow’s CMDB to give you and your team rich,
relevant data to make informed decisions across your on-prem and cloud
infrastructure. Increase the data share frequency and wealth of information
on each resource in the form of Facts, collected by the Puppet Agent and
shared directly into the ServiceNow CMDB for real-time data advantage.

*Key features/changes:*
·  Users are able to import data to ServiceNow from Multiple Puppet
Enterprises using this version. ·  Certified to ServiceNow Tokyo *Support
Contact*

Puppet Integrations Engineering

team-...@puppet.com
*Find out more* https://www.puppet.com/integrations/servicenow

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nF%3DzJERkSZRx9dtc0_JQhC0jZWQCk5BGrOUPWWwanVP5w%40mail.gmail.com.

[Puppet Users] Puppet Content and Tooling Releases

[Puppet Product Updates]

Puppet Content and Tooling Releases
Supported modules

puppetlabs-tomcat v6.4.1 and v.6.4.0

The Tomcat module installs, deploys, and configures Apache Tomcat web
services.
Key
features/changes:
Added

   - Added abbility to set attributes on apache context



Fixed

   -  Remove support for RedHat6 / OracleLinux6 / Scientific6

Full changelog v6.4.0 to v6.4.1

Full changelog V6.3.0 to v6.4.0

Feedback

https://github.com/puppetlabs/puppetlabs-tomcat/issues

puppetlabs-acl v9.0.2

The acl module lets you use Puppet to manage Access Control Lists (ACLs) on
Windows.

Windows uses Access Control Lists (ACLs) to store permissions information.
An ACL is typically made up of a series of Access Control Entries (ACEs),
representing individual permissions. The acl module adds a type and
provider to let you manage all that information through Puppet.
Key
features/changes Fixed

   - Updated PDK and Puppet support versions

Full changelog

Feedback

https://github.com/puppetlabs/puppetlabs-apt/issues
puppet-exec v2.2.1

A ruby based implementation of a Language Server and Debug Server for the
Puppet Language. This tool can then be used within editors to validate and
debug Puppet code.
Key
features/changes Fixed

   - Remove support for RedHat6 / OracleLinux6 / Debian 9
   - Fix NoMethodError in puppet_strings_helper.rb

Full changelog

Feedback

https://github.com/puppetlabs/puppet-exec/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nHeXy-nK_%3Do1zJ3Lr3%2BYAOy9F2XhGEOhOBzAGyD0YXznA%40mail.gmail.com.

[Puppet Users] Puppet Content and Tooling Releases

[Puppet Product Updates]

Puppet Content and Tooling Releases
Supported modules
puppetlabs-chocolatey
v7.0.1

The chocolatey module is a package provider allowing for the use of
Chocolatey in package resources. Chocolatey is the largest online registry
of Windows packages.
Key
features/changes: Fixed

   - Resolved issues with sensitive parameters being exposed in debugging
   logs.

Full changelog

Feedback

https://github.com/puppetlabs/puppetlabs-chocolatey/issues
puppetlabs-apt
v9.0.2

The apt module Provides an interface for managing APT (Advanced Package
Tool) source, key, and definitions with Puppet. APT is a package manager
available on Debian, Ubuntu, and several other operating systems
Key
features/changes Fixed

   - Allowed for package names to contain dots when marking removed global
   scoping of variables apt::pin default changed from empty string to undef

Full changelog 
Feedback

https://github.com/puppetlabs/puppetlabs-apt/issues
Development tools
puppet-editor-services
v1.3.1

A ruby based implementation of a Language Server and Debug Server for the
Puppet Language. This tool can then be used within editors to validate and
debug Puppet code.
Key
features/changes Fixed

   - Resolved depency issues by using a realpath
   - Fix NoMethodError in puppet_strings_helper.rb

Full changelog

Feedback

https://github.com/puppetlabs/puppet-editor-services/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nGEj6BFHk4f3C7KQFBRZ7M1kd%2BotBFgQ4fqr6m-A_V1Tw%40mail.gmail.com.

[Puppet Users] PDK 2.7 has been released

[Puppet Product Updates]

The Puppet Development toolkit (PDK) provides integrated testing tools and
a command line interface to help you develop, validate, and test modules

*Where you can find it:*
- https://www.puppet.com/downloads/puppet-development-kit
- https://community.chocolatey.org/packages/pdk/2.7.0.0
- https://www.puppet.com/docs/pdk/2.x/pdk_upgrading.html
- https://www.puppet.com/docs/pdk/2.x/release_notes_pdk.html

*Key features/changes:*

- Added

A RedHat 9 compatible package has been added.
A new Puppet validator for Bolt plans has been added by community member
jay7x.
PDK Templates have been updated to 2.7.2.
Puppet 7.23 has been added to the packages.
Ruby 2.7.7 is now the default runtime used by packaged versions of PDK.
The minimum ruby requirement has been raised to 2.5.9./op


- Changed

PDK no longer ships with OSX 10.15 packages.

Legacy i18n support has been removed.

- Fixed

Selecting a Puppet Enterprise version with PDK_PE_VERSION will resolve the
latest puppet gem relative to the PE release.

The vendored puppet-lint plugins have been updated to their latest
compatible versions. This resolves an issue that top scope facts to be
formatted incorrectly.

Deprecation warnings for bundle show will no longer be displayed when using
the release command.


*Feedback:*
- https://github.com/puppetlabs/pdk/issues
- https://github.com/puppetlabs/pdk-templates/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nGSmUaxMzB6c1TFu1G3-tkEsZMcBSkbBtTWGvL%3D6Qw90g%40mail.gmail.com.

[Puppet Users] Supported module releases puppet-lint (3.3.0) puppetlabs-wsus_client (5.0.0) puppetlabs-sqlserver (3.3.0)

[Puppet Product Updates]

*Supported modules released* *puppet-lint 3.3.0 has been released*
 *What it is:*
 Puppet Lint tests Puppet code against the recommended Puppet language
style guide . *Where
you can find it:*
- https://rubygems.org/gems/puppet-lint
- Release notes:
https://github.com/puppetlabs/puppet-lint/blob/main/CHANGELOG.md *Key
features/changes:*
 - Fixed

Corrects legacy macOS fact interpretation issues corrected in
https://github.com/puppetlabs/puppet-lint/pull/103 by
https://github.com/mhashizume

 *Feedback:*
 - https://github.com/puppetlabs/puppet-lint/issues

*puppetlabs-wsus_client 5.0.0 has been released*
*What it is: *
wsus_client is a module used to Manage WSUS (Windows Server Update Service)
settings for client nodes

*Where you can find it:*
 - https://forge.puppet.com/modules/puppetlabs/wsus_client/readme
 -
https://github.com/puppetlabs/puppetlabs-wsus_client/blob/main/CHANGELOG.md

*Key features/changes:*
- Added

Support for Windows 2022

- Changed

Dropped support for windows 7, 8, 2008 Server and 2008 Server R2
Set parameters of module to use data types

*Feedback:*
-  https://github.com/puppetlabs/puppetlabs-wsus_client/issues
*puppetlabs-sqlserver 3.3.0 has been released**What it is: *sqlserver is a
module that manages MS SQL Server 2012, 2014, 2016, 2017, 2019 and 2022 on
Windows systems

*Where you can find it:*
- https://forge.puppet.com/modules/puppetlabs/sqlserver/readme
- https://github.com/puppetlabs/puppetlabs-sqlserver/blob/main/CHANGELOG.md

 *Key features/changes:*
 Added
 - Support for SQL Server 2022
*Feedback:*
- https://github.com/puppetlabs/puppetlabs-sqlserver/issues

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANOD9nGs4Jf7XCAmAKVUZP_dZkYYVXfOUqe6mVKoha_FKX%3D0tw%40mail.gmail.com.

[Puppet Users] Puppet 6 End Of Life Announcement

[Puppet Product Updates]

Greetings!

Puppet 6.0 was released on September 18, 2018, and has been
receiving critical security updates only since September 27, 2022
. As of today,
Puppet 6.x has reached end-of-life (EOL) and will no longer receive any
updates.

Users are encouraged to upgrade to Puppet 7.x as soon as possible. The
Puppet 7.x stream will receive regular updates until August 2024, at which
point it will only receive critical security patches.

Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACkW_L6F-b1E0negGu_vjxa0embfeq4%2BVLGQ%3D8vH%2BxaMT8BPSQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.21.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.21.0, is now available!



The release contains minor enhancements, and bug fixes including:


*Enhancements:*


   - Allow legacy facts to be excluded
   - Allow omission of unchanged resources from reports


*Resolved issues:*

   - Tasks are not listed when a single task in an environment has
   malformed metadata
   - Purging SSH keys on a user resource fails when alias is used

*Security:*

   - Updates puppet-agent's Ruby to 2.7.7, addressing CVE-2021-33621
   - Update libxml2 to 2.10.3
   - osx-10.15-x86_64 - Updates Nokogiri to 1.13.9, which addresses
   CVE-2022-2309, CVE-2022-40304, and CVE-2022-40303 in Nokogiri's vendored
   libxml2 and CVE-2022-37434 in Nokogiri's vendored zlib



For the full list of changes and detailed descriptions, check out the
release notes:
https://puppet.com/docs/puppet/7/release_notes_puppet.html#release_notes_puppet_x-7-21-0


Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmJRiQsoRrPu8bPBL4hdcozpXk3A9QGEu8UHFP4cFTyRnw%40mail.gmail.com.

[Puppet Users] Open Source Puppet to stop supporting JDK 8

[Puppet Product Updates]

Greetings,

This note is to inform you that starting with our February release of Open
Source Puppet 8, we'll be dropping support for JDK 8.

Best regards,
Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmLjz34V7LToXxnTCrBb3GzA2LJkaRiWj-76LhQwtqPXQw%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.7.1 is now available!

[Puppet Product Updates]

The latest patch release for Puppet Enterprise, 2021.7.1, is now available!



This is a backward-compatible release that contains enhancements and
resolved issues from our previous major release. The following are a few
highlights. Please refer to the release notes HERE

for
a complete list and full descriptions.


Enhancements in this release include:


   - Stop in-progress plans - Use POST /command/stop_plan to stop an
   orchestrator plan job that is currently running.


This version adds support for these platforms:


Agent


   - Fedora 36

Patch management


   - Fedora 36

Deprecations and removals on this version


Deprecated agent platforms


   - Debian 9
   - Fedora 32, 34

Deprecated patch management platforms


   - Debian 9
   - Fedora 34


Resolved in this release:

   - Deactivated scheduled jobs could still run.
   - Orchestrator didn't properly periodically prune jobs
   - Improved PuppetDB disaster recovery sync performance
   - Empty task metadata files prevented you from running tasks in the
   console
   - Some puppet infrastructure commands failed when restarting the puppet
   service



Check out the release notes for a complete list of changes and full
descriptions:
https://puppet.com/docs/pe/2019.8/release_notes_pe.html#release-notes-pe-x-y-12




Download PE 2021.7.1 here:
https://puppet.com/try-puppet/puppet-enterprise/download/

As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKV748T11-hbrfedYy%3DtrM2cvNEaTVBd9LEV4KjapUQOw%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.20.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.20.0, is now available!



The release contains minor enhancements, and bug fixes including:


Agent 7.20.0

   - Bumps resource-api gem to 1.8.16
   - Fixed a bug in the Augeas component of the puppet-agent platform on
   macOS. *Contributed by Puppet community member h0tw1r3*
   - puppet-agent 7.19.0 had a broken Augeas packaged with it. This is
   fixed in puppet-agent 7.20.0
   - This release removes support for Debian 9 (x86 and x86-64), Fedora 34
   and 32.



PuppetDB 7.11.0

   - The org.postgresql/postgresql driver has been updated to version
   42.4.1 to address CVE-2022-31197, which is an SQL injection risk that
   according to the CVE report, can only be exploited if an attacker controls
   the database to the extent that they can adjust relevant tables to have
   "malicious" column names.



For the full list of changes and detailed descriptions, check out the
release notes:
https://puppet.com/docs/puppet/7/release_notes_puppet.html#release_notes_puppet_x-7-20-0


Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmJ3W2ewNjBj0ZoFcYYhTg9BncaumObyKXtkGuiTNFtTpg%40mail.gmail.com.

[Puppet Users] Puppet 6 End Of Life Announcement

[Puppet Product Updates]

Greetings!

Puppet 6.0 was released on September 18, 2018, and as of today, Puppet 6.x
will receive only critical security updates and will reach end-of-life
(EOL) February 28, 2023. After that date, Puppet 6.x will no longer receive
any updates.

Users are encouraged to upgrade to Puppet 7.x as soon as possible. The
Puppet 7.x stream will receive regular updates until August 2024, at which
point it will only receive critical security patches.

Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmLgMy05ytWZoo503M3aFnnd-zEX2X%3DkYT9nw3DVFSwSDQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.19.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.19.0, is now available!



Note: New versions of Puppet now release every six weeks rather than every
4 weeks.



The release contains new features, minor enhancements, and bug fixes
including:



Agent 7.19.0

   -

   Adds support for Fedora 36 (x86_64)
   -

   Bumped Augeas to 1.13.0 for all supported platforms except for Solaris
   and AIX



Server 7.9.1

   -

   The included Dropsonde gem has been upgraded to 0.0.8, which adds the
   ability to list unused modules to the telemetry client report generator



Facter 4.2.12

   -

   Facter now supports ERB changes introduced in Ruby 3.1



Resolved Issues:

   -

   Reports sent to PuppetDB using the Oj JSON backend are now properly
   formatted
   -

   `puppet module list --render-as json` now includes information about
   unmet dependencies
   -

   Puppet now handles misconfigured `/proc` filesystems correctly
   -

   Puppet now passes ERB arguments as keywords
   -

   Enabled YAML anchors in Facter 4, a feature that was available
   previously in Facter 3. Additionally, testing was added to ensure Facter
   continues to behave as expected when handling YAML anchors



Security:

   -

   FIPS OpenSSL: disable c_rehash binary Fixed CVE-2022-1292 and
   CVE-2022-2068





For the full list of changes and detailed descriptions, check out the
release notes:
https://puppet.com/docs/puppet/7/release_notes_puppet.html#release_notes_puppet_x-7-19-0


Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2Bm%2B5rWWjH%3DnmsHfoqbQ0in7tD-4qgsnXn9LWiZgj_UvZrA%40mail.gmail.com.

[Puppet Users] New LTS release of Puppet Enterprise version 2021.7.0 is now available!

[Puppet Product Updates]

We're excited to announce the new LTS release of Puppet Enterprise, version
2021.7. This new LTS release provides many new features and enhancements to
help you and your team scale your enterprise while curtailing cost. Please
refer to the Release Notes HERE
.
The following are some highlights:



New features in this release include:


   -

   Force stop in-progress Puppet runs
   -

   pe_status_check module bundled with PE
   -

   New Orchestrator scheduling API
   -

   Use the RBAC API to set the disclaimer text on the console login page
   -

   Automatically sync LDAP user details and group membership
   -

   Stop LDAP users from logging in if they have no group membership
   -

   Metrics API v2 documentation
   -

   Disaster recovery support for FIPS platforms


Enhancements in this release include:


   -

   Orchestrator API endpoints return "total": 0 if there are no jobs
   -

   Activity service API /v2/events endpoint returns more information for
   orchestrator events
   -

   We are now shipping JRuby 9.3.4.0.
   -

   We updated the PostgreSQL driver in some PE components to address
   CVE-2022-31197.


This version adds support for these platforms:

Agent

   -

   macOS 12 M1
   -

   Ubuntu (General Availability kernels) 22.04 x86_64
   -

   Microsoft Windows 11 x86, x64

Client tools

   -

   Ubuntu (General Availability kernels) 22.04 x86_64
   -

   macOS 12 M1, M2

Patch management

   -

   Ubuntu (General Availability kernels) 22.04 x86_64
   -

   Microsoft Windows 11 x64



Resolved in this release:

   -

   Code Manager couldn't fetch code on FIPS platforms
   -

   An unreachable replica consumed all of the primary server's disk space
   -

   Orchestrator ignored _noop when passed to run_task() through a plan
   -

   Some RBAC endpoints returned an incorrect Content-Type
   -

   LDAP with anonymous binding sometimes prevented Console Services from
   starting or restarting





Check out the release notes for a complete list of changes and full
descriptions:
https://puppet.com/docs/pe/2021.7/release_notes_pe.html#release_notes_pe_x-7



Download PE 2021.7.0 here:
https://puppet.com/try-puppet/puppet-enterprise/download/


As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2Bm%2B_%3D9P879Dx16ePszar%2BopQaDzXBuQcGi9__KzTWLNSmA%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.12 is now available!

[Puppet Product Updates]

The latest patch release for Puppet Enterprise, 2019.8.12, is now
available!



This is a backward-compatible release that contains enhancements, and
resolved issues from all previous major releases. The following are a few
highlights. Please refer to the release notes HERE

for
a complete list and full descriptions.

Enhancements in this release include:

   -

   Orchestrator API endpoints return "total": 0 if there are no jobs
   -

   We updated the PostgreSQL driver in some PE component to address
   CVE-2022-31197


This version adds support for these platforms:

Agent

   -

   macOS 12 M1
   -

   Ubuntu (General Availability kernels) 22.04 x86_64
   -

   Microsoft Windows 11 x86, x64

Client tools

   -

   Ubuntu (General Availability kernels) 22.04 x86_64
   -

   macOS 12 M1, M2

Patch management

   -

   Ubuntu (General Availability kernels) 22.04 x86_64
   -

   Microsoft Windows 11 x64



Resolved in this release:

   -

   Code Manager couldn't fetch code on FIPS platforms
   -

   Orchestrator ignored _noop when passed to run_task() through a plan
   -

   Orchestrator doesn't restart unexpectedly during the
   convert_legacy_compiler plan
   -

   Orchestrator couldn't run tasks within modules named tasks or scripts





Check out the release notes for a complete list of changes and full
descriptions:
https://puppet.com/docs/pe/2019.8/release_notes_pe.html#release-notes-pe-x-y-12




Download PE 2019.8.12 here:
https://puppet.com/misc/pe-files/previous-releases/2019.8.12



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

Puppet

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKg%3D1_7vo9A%3DGHbUiWGUptK-3UvTcqcJfFiSHtLMuXRVQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.28.0 is now available!

[Puppet Product Updates]

The release contains new features, minor enhancements, and bug fixes
including:



Agent 6.28.0

   -

   Adds support for Ubuntu 22.04 (x86_64), macOS 12 (M1), and Windows 11
   Enterprise (x86_64)
   -

   Puppet Agent now reloads its CA and CRL bundles every 30 minutes during
   each run. Previously it only loaded it when the process started, which
   meant the service had to be restarted if the CA/CRL files changed on disk



PuppetDB 6.22.0

   -

   Query logging has been improved when log-queries is set to true. Now
   queries are logged with their UUID before they are parsed which makes
   debugging easier when there are PQL parsing issues
   -

   Fixed a bug that was introduced in 6.21.0 and 7.10.1 which caused
   upgrade failures with PostgreSQL hot standbys. The method of disabling the
   jit has been changed to avoid the problem



Server 6.20.0

   -

   puppetserver http client respects include_system_store option. Puppet
   Server's Ruby HTTP client now supports loading certificates from the system
   trust store that is included with Puppet Agent. It also supports loading
   certs from a file or Java cert store at an arbitrary location via the
   ssl_trust_store setting
   -

   When the puppet user and group are created on rpm-based systems, they
   are now assigned a static UID/GID of 52.





For the full list of changes and additional details, check out the release
notes:

https://puppet.com/docs/puppet/6/release_notes_puppet.html#release_notes_puppet_x-28-0

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKah%3D5%2BaTh7WR%2Bra8am_OvvX15k3gyYQQj%3Dsru_HoZ-Bg%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.18.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.18.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



Agent 7.18.0

   -

   Adds support for Ubuntu 22.04 (x86_64), macOS 12 (M1), and Windows 11
   Enterprise (x86_64)
   -

   Puppet agent --disable is ignored with cron puppet agent (splay). Puppet
   agent now checks the disabled lock file after sleeping due to splay



PuppetDB 7.11.0

   -

   Query logging has been improved when log-queries is set to true. Now
   queries are logged with their UUID before they are parsed which makes
   debugging easier when there are PQL parsing issues
   -

   Fixed a bug that was introduced in 6.21.0 and 7.10.1 which caused
   upgrade failures with PostgreSQL hot standbys. The method of disabling the
   jit has been changed to avoid the problem



Server 7.9.0

   -

   Puppet Server now uses JRuby 9.3.4.0





For the full list of changes and detailed descriptions, check out the
release notes:

https://puppet.com/docs/puppet/7/release_notes_puppet.html#release_notes_puppet_x-7-18-0

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2Bm%2Bh-FJKe0KU8r1s_OsFuxKrWo8WPLh47KFDG51ZOdQ9JA%40mail.gmail.com.

[Puppet Users] Bolt 3.25.0 is now available

[Puppet Product Updates]

VERSION 3.25.0

*in this release*

✨  *new features*

   - The ApplyResult data type in plans now includes a catalog function to
   view the catalog used during an apply. For more information about this data
   type, see the reference page
   
   .
   - Bolt's module resolution feature now supports installing git modules
   from most git sources, not just public GitHub repositories. For more
   information about the module resolution feature, see the documentation
   .
   - Group names and target alias names now permit a larger set of
   characters. Now, the only restricted characters are whitespace characters
   and commas.
   - Bolt now ships with the bash_task_helper module, which includes a
   library to help you write tasks in Bash. For more information about the
   task helpers that Bolt ships with, see the documentation
   .
   - Bolt now ships with puppet_agent 4.12.1
   
and stdlib 8.4.0
    .

🔧  *bug fixes*

   - Bolt no longer permits target names to include whitespace characters
   or commas. Previously, these characters were allowed, but Bolt would not be
   able to retrieve them from the inventory by name.
   - Bolt now configures a proxy when module-install.proxy is set and it
   retrieves metadata for git-based modules. Previously, Bolt was only
   configuring a proxy when it resolved and installed modules.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUKc65siGOmWrK2oUuv%2BMBea_fMONov7ysWR1oRTG4pNA%40mail.gmail.com.

[Puppet Users] Bolt 3.24.0 is now available

[Puppet Product Updates]

VERSION 3.24.0

*in this release*

✨  *new features*

   - Bolt now supports extended glob patterns for target matching when
   using the --targets command-line option. For more information on using
   glob patterns, see the documentation
   

   .
   *Contributed by Bolt user Yury Bushmelev!*
   - The lxd transport now supports the interpreters configuration option.
   For a full list of transport configuration options, see the reference
   page
   .
   *Contributed by Bolt user Jonas De Moor!*
   - Bolt now ships with puppetlabs-reboot 4.2.0 as part of its bundled
   modules.

🔧  *bug fixes*

   - Bolt now opens a new shell instance each time it runs a command over
   winrm. Previously, Bolt used a single shell instance to run all
   commands, preventing Bolt from properly cleaning up temporary files in some
   instances.
   - Bolt no longer errors when creating secret keys and using the rainbow
   format.
   - Bolt no longer submits sensitive parameter values to the PE
   Orchestrator service when running plans over pcp.

🚨  *removals*

   - Bolt no longer ships packages for Fedora 32 and Ubuntu 16.04.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUFPTTq9Cqs-rPE13v8uuHDX5nt5e7DDijXokXzYzp%2BGg%40mail.gmail.com.

[Puppet Users] Bolt 3.23.1 is now available

[Puppet Product Updates]

VERSION 3.23.1

*in this release*

🔧  *bug fixes*

   - Bolt now supports local.extensions configuration when running on
   Windows. Previously, this configuration option was not enabled, preventing
   some types of tasks from running.
   - The puppetdb plugin now correctly collects facts from a named PuppetDB
   instance when one is specified using the instance option. Previously,
   the plugin would collect facts from the default PuppetDB instance instead
   of the named instance.

VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pVY8iTij3TUvyKLYV154F2E8rGrhy_g-entcOEUWSwxbA%40mail.gmail.com.

[Puppet Users] Bolt 3.23.0 is now available

[Puppet Product Updates]

VERSION 3.23.0

*in this release*

✨  *new features*

   - Bolt can now connect to multiple PuppetDB instances. You can also
   specify a named PuppetDB instance to connect to whenever Bolt connects to
   PuppetDB. For more information on using this feature, see the
   documentation
   

   .
   - Bolt now ships packages for RedHat 9, macOS 12 (Monterey), and SLES 15.
   - The bolt gem is now compatible with Ruby 3.x.
   - The following bundled modules have been updated to their latest
   versions:
  - package 2.2.0
  
  - puppet_agent 4.11.0
  
  - puppet_conf 1.3.0
  
  - ruby_task_helper 0.6.1
  
  - scheduled_task 3.1.0
  
  - service 2.2.0
  
  - stdlib 8.2.0
  

🔧  *bug fixes*

   - The bolt plan show  and Get-BoltPlan -Name  commands now
   include a plan's docstring in the output. Previously, Bolt did not display
   the plan's docstring if the plan included a @summary tag.
   - Bolt no longer errors when running a task in no-operation mode over
   the pcp transport.

🚨  *removals*

   - Bolt no longer ships new packages for macOS 10.15 (Catalina).


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pXY4gEX%3DeqwwVWWyKB%3DFSqXnkbVcBxfz%2B9cbB_SvKeQgw%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.17.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.17.0, is now available!



The release contains enhancements and vulnerability fixes, including (Release
Notes ):

Enhancements:

   -

   Add `virt-what` and`dmidecode` in Puppet Agent
   -

   Puppet Agent now reloads its CA and CRL bundles every 30 minutes during
   each run
   -

   Resolve deferred values on demand instead of at catalog read time

Resolved Issues:


   - Remove compiler errors for deferred function mismatched types
   - Puppet's http client can now establish a mutually authenticated TLS
   connection when passing "include_system_store: true" such as when
   retrieving file content from HTTPS servers.
   - Yum provider now accepts `disablerepo`, `enablerepo`, and
   `disableexcludes` install options if a range is specified

Security:

   -

   Fix for CVE-2022-29181: Nokogiri vulnerability



We would like to thank the following Puppet community members for their
contributions to this release: jplindquist 
and lollipopman ,



*For the full list of changes* and detailed descriptions, check out the
release notes:



https://puppet.com/docs/puppet/7/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2Bm%2BYX9mbTKSUgUTrrYofP7u4zgWaz0_RMoSD%3Dd-CEwNzCw%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.11 is now available!

[Puppet Product Updates]

The latest patch release for the current Long Term Support (LTS) version of
Puppet Enterprise, 2019.8.11, is now available!



This is a backward-compatible release that contains new features,
enhancements, and resolved issues from all previous major releases. The
following are a few highlights. Please refer to the release notes HERE
 for a
complete list and full descriptions.


*CAUTION*: If you use the puppet_agent module to upgrade your agents,
please wait to upgrade to 2019.8.11 until we release a new version of the
puppet_agent module in the next few days. We've identified an issue that
can cause the upgrade to fail when using this module.



New features in this release include:


   -

   Lockless code deploys are no longer experimental
   -

   Run plans without blocking code deployments


Enhancements in this release include:


   -

   Optimized some PuppetDB queries
   -

   Upgraded Bouncy Castle to 1.70
   -

   Report compilation failure results for apply blocks


This version adds support for these platforms:

Primary server

   -

   FIPS 140-2 compliant Red Hat Enterprise Linux 8 x86_64
   -

   SUSE Linux Enterprise Server 15 x86_64
   -

   Ubuntu (General Availability kernels) 20.04 x86_64

Agent

   -

   macOS 12 x86_64



Resolved in this release:



   -

   Code Manager didn't delete spec directories
   -

  Code Manager deploys failed to delete spec directories due to an
  issue with r10k. To fix this, we upgraded r10k to version 3.14.1.
  -

   LDAP connection timeout setting was ignored
   -

  In the console, the LDAP connect_timeout field wasn't correctly
  passed to the connection attempt and, as a result, the value
wasn't applied
  in the LDAP configuration.
  -

   The plan that upgrades the secondary node sometimes failed
   -

  When running puppet infrastructure upgrade compiler or puppet
  infrastructure upgrade replica, the plan that upgrades the secondary node
  sometimes failed on the step where install.bash runs on the node
to update
  the agent.





Check out the release notes:
https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html



Download PE 2019.8.11 here:

https://puppet.com/misc/pe-files/previous-releases/2019.8.11



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmJwrhfoih8jhjjpg1Q_C5nSrFA_fFX_j-cQBijg4X%3D4DQ%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.6 is now available!

[Puppet Product Updates]

Greetings

The latest release for the Puppet Enterprise release track, PE 2021.6, is
now available! This release incorporates new features, enhancements, and
resolved issues from all previous major releases. The following are a few
highlights. Please refer to the release notes HERE
 for a complete list
and full descriptions.



New features in this release include:


   -

   PE version 2021.6 upgrades PostgreSQL to version 14
   -

   Lockless code deploys are no longer experimental
   -

   Run plans without blocking code deployments
   -

   RBAC API v2 GET /users endpoint


Enhancements in this release include:


   -

   Optimized some PuppetDB queries
   -

   Upgraded Bouncy Castle to 1.70
   -

   Report compilation failure results for apply blocks


This version adds support for these platforms:

Primary server

   -

   FIPS 140-2 compliant Red Hat Enterprise Linux 8 x86_64
   -

   SUSE Linux Enterprise Server 15 x86_64
   -

   Ubuntu (General Availability kernels) 20.04 x86_64

Agent

   -

   macOS 12 x86_64




Resolved in this release:

   -

   Code Manager didn't delete spec directories
   -

  Code Manager deployments failed to delete spec directories due to an
  issue with r10k. To fix this, we upgraded r10k to version 3.14.1.
  -

   LDAP connection timeout setting was ignored
   -

  In the console, the LDAP ‘connect_timeout’ field wasn't correctly
  passed to the connection attempt and, as a result, the value
wasn't applied
  in the LDAP configuration.
  -

   The plan that upgrades the secondary node sometimes failed
   -

  When running puppet infrastructure upgrade compiler or puppet
  infrastructure upgrade replica, the plan that upgrades the secondary node
  sometimes failed on the step where install.bash runs on the node
to update
  the agent.





Check out the release notes:
https://puppet.com/docs/pe/2021.6/pe_user_guide.html



Download PE 2021.6 here:

https://puppet.com/try-puppet/puppet-enterprise/download/


As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmLrPJkAX-OOVsaEZPP1hYeEVgAHaWJ5SfKngD1LuTcuVw%40mail.gmail.com.

[Puppet Users] Correction: Puppet Platform 6.27.1 (not 6.27.0) is now available!

[Puppet Product Updates]

*Correction:* An email sent earlier erroneously said that Puppet Platform
*6.27.0* was released. This should have said Puppet Platform *6.27.1*.
Thanks for your understanding!

On Tue, Apr 19, 2022 at 3:49 PM Puppet Product Updates <
puppet-product-upda...@puppet.com> wrote:

> The release contains new features, minor enhancements, and bug fixes
> including:
>
>
>
> Agent 6.27.1
>
>-
>
>Adds macOS 12 (x86_64) as a supported Agent platform
>-
>
>Allows use of puppet certificate for client HTTPS authentication with
>external CAs
>
>
>
> PuppetDB 6.21.0
>
>-
>
>Ubuntu 20.04 and SUSE Linux Enterprise 15 are now supported.
>-
>
>PuppetDB will no longer run a garbage collection on startup. This may
>substantially reduce the time required before PuppetDB begins accepting
>commands and queries.
>-
>
>PuppetDB should require much less time and memory when parsing some
>PQL queries
>-
>
>The fact path GC now runs no more than once every 24 hours by default.
>This should be much less expensive in most cases, in exchange for a
>potentially slower response to the disappearance of individual fact paths.
>
>
>
> Server 6.19.0
>
>-
>
>Adds SUSE Linux Enterprise 15 as supported Server platform
>-
>
>Server CA now supports using a type 2 key identifier
>
>
>
>
> For the full list of changes, check out the release notes:
> https://puppet.com/docs/puppet/6/release_notes_osp.html
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMW2%3DMTFtgAAJGzqisvOrBXdX_qUac6%2BRCWba30ODRuRfA%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.16.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.16.0, is now available!



The release contains enhancements and vulnerability fixes, including:

Agent 7.16.0

   -

   Adds macOS 12 (x86_64) as a supported Agent platform
   -

   Allows use of puppet certificate for client HTTPS authentication with
   external CAs



PuppetDB 7.10.1

   -

   Ubuntu 20.04 and SUSE Linux Enterprise 15 are now supported
   -

   PuppetDB should require much less time and memory when parsing some PQL
   queries



Server 7.7.0

   -

   Adds SUSE Linux Enterprise 15 as supported Server platform
   -

   Change Dropsonde telemetry to Opt-out. Metrics will now be collected
   with Dropsonde by default.



For the full list of changes, check out the release notes:



https://puppet.com/docs/puppet/7/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMU4aUT7c1c0x9%2BT1bc-q3S8heTc-hjXgAEOq90j_YHODQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.27.0 is now available!

[Puppet Product Updates]

The release contains new features, minor enhancements, and bug fixes
including:



Agent 6.27.1

   -

   Adds macOS 12 (x86_64) as a supported Agent platform
   -

   Allows use of puppet certificate for client HTTPS authentication with
   external CAs



PuppetDB 6.21.0

   -

   Ubuntu 20.04 and SUSE Linux Enterprise 15 are now supported.
   -

   PuppetDB will no longer run a garbage collection on startup. This may
   substantially reduce the time required before PuppetDB begins accepting
   commands and queries.
   -

   PuppetDB should require much less time and memory when parsing some PQL
   queries
   -

   The fact path GC now runs no more than once every 24 hours by default.
   This should be much less expensive in most cases, in exchange for a
   potentially slower response to the disappearance of individual fact paths.



Server 6.19.0

   -

   Adds SUSE Linux Enterprise 15 as supported Server platform
   -

   Server CA now supports using a type 2 key identifier




For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/6/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMXnKW_9J4%2BzksyPUdLXAEr-rqTuKmpwm0dWJyS5%3Dsc8hA%40mail.gmail.com.

[Puppet Users] Bolt 3.22.1 is now available

[Puppet Product Updates]

VERSION 3.22.1

🔧  *bug fixes*

   - Bolt's bundled Ruby was being erroneously codesigned when building
   packages for macOS platforms, causing Bolt to fail when connecting to
   targets over SSH. Bolt's bundled Ruby is no longer codesigned.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pWUq-Cd7AUE739pBQC%2BC0H%3DcMwa23SSnrf2-WPO_O%3Dq%2Bg%40mail.gmail.com.

[Puppet Users] Bolt 3.22.0 is now available

[Puppet Product Updates]

VERSION 3.22.0

*in this release*

✨  *new features*

   - Bolt now warns if it finds a bolt-plugin.json file in a plugin module
   instead of a bolt_plugin.json file.
   - Bolt can now read manifests from a named pipe when using the
   bolt apply command, treating them as files.
   - You can now configure the path to a project's rerun file using the
   rerunfile setting in the project configuration file.
   - The env_var plugin can now parse data as JSON when you set the
   plugin's new json setting to true.

🔧  *bug fixes*

   - The native SSH transport is now more portable and adds a double-dash
   separator  before commands to execute.
   - The puppetdb plugin now supports indexing into nested arrays when
   resolving facts.

VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pXGAAuZ0NwwpVex8eFjRaw3Ug%2B7VPMudyJrsfgatvUZzQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.15.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.15.0, is now available!



The release contains enhancements and vulnerability fixes, including:

Agent 7.15.0

   -

   Fixes a regressions introduced in previous releases


   -

   On Windows, facter and hiera gemspecs are now installed
   -

   On macOS, updated nokogiri gem for CVE-2022-23308

PuppetDB 7.10.0

   -

   PuppetDB will no longer run a garbage collection on startup.  This may
   substantially reduce the time required before PuppetDB begins accepting
   commands and queries.



Server 7.6.1

   -

   Server CA now supports usage as an Intermediate Authority using a type 2
   key identifier



For the full list of changes, check out the release notes:



https://puppet.com/docs/puppet/7/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmLF%2BPfzOOApBrvM1Na%2Br7AMrtS_LbYLoHEDPhAzj9fFzg%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.10 is now available!

[Puppet Product Updates]

The latest patch release for the current Long Term Support (LTS) version of
Puppet Enterprise, 2019.8.10, is now available!



This is a backward-compatible release that contains enhancements and bug
fixes, including:



Enhancements:

   -

   Bypass node verification failure when primary server certificates are
   damaged. You can use --force to bypass node verification failure and
   force certificate regeneration when your primary server certificates are
   damaged.
   -

   Simplified login error message. The Puppet Enterprise (PE) console login
   error message instructs the user to contact an administrator rather than
   consult the console-services log.
   -

   Improved disk usage when syncing certificate authority data. Disk usage
   is better when syncing certificate authority data between the primary and
   replica.
   -

   Agent support for:
   -

  Microsoft Windows Server 2022 x86_64
  -

  Red Hat Enterprise Linux 9 x86_64
  -

   Patch management:
   -

  Amazon Linux 2



Deprecations and removals:

Support for these platforms is deprecated in this release:

   -

   Primary server:
   -

  CentOS 8
  -

   Agent:
   -

  CentOS 8



Resolved in this release:



   -

   Expired GPG key caused install failures. The GPG key bundled with PE
   versions prior to 2019.8.4 expired on 17 August 2021, which could cause a
   failure when PE packages are being added to the system. Customers upgrading
   to a newer version are no longer affected.
   -

   Packages were not marked as automatically installed by APT if you set
   security_only to true. When running the pe_patch::patch_server task with
   the security_only parameter set to true, packages were not marked as being
   automatically installed by APT. This caused problems if you rely on this
   marking for APT autoremove to remove old packages. The patch_server task
   now marks packages as automatically installed, regardless of the
   security_only parameter.
   -

   r10k can recover from typos in the config or Puppetfile. r10k now
   updates its cache repos when the remote URL changes. This allows r10k to
   recover from typos in the config or Puppetfile.
   -

   Couldn't complete restoration if the r10k_remote parameter wasn't set. The
   r10k_remote parameter wasn't set when restoring a backup with scope set to
   certs, code, or puppetdb. This prevented you from finishing restoration
   because the commands necessary to finish restoring your primary server did
   not print.
   -

   The fail_plan function didn't show custom error information. The
   fail_plan function ignored the kind and details parameters, which are used
   to specify custom, machine-parseable information about an error.
   -

   Scheduled jobs failed on FIPS installs. Scheduled jobs, including tasks
   and plans, couldn't run or be listed on FIPS installs of PE and resulted in
   the error javax.crypto.BadPaddingException.



Check out the release notes:
https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html



Important note: If you are using Continuous Delivery for PE, upgrade to
CD4PE 4.8.2 prior to upgrading to Puppet Enterprise 2019.8.10. We resolved
a PuppetDB issue causing the generation of new fact charts on the Nodes
page to fail.



Download PE 2019.8.10 here:

https://puppet.com/misc/pe-files/previous-releases/2019.8.10



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmJBef83fiV2ziQZehDWHdnW4syFfMjgYhSyxk1gTvJ2Vw%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.5 is now available!

[Puppet Product Updates]

The latest release for the Puppet Enterprise release track, PE 2021.5, is
now available!



Enhancements in this release include:


   -

   Bypass node verification failure when primary server certificates are
   damaged. You can use --force to bypass node verification failure and
   force certificate regeneration when your primary server certificates are
   damaged.
   -

   Improved disk usage when syncing certificate authority data. Disk usage
   is better when syncing certificate authority data between the primary and
   replica.
   -

   Primary server support for:
   -

  Amazon Linux 2
  -

   Agent support for:
   -

  Microsoft Windows Server 2022 x86_64
  -

  Red Hat Enterprise Linux 9 x86_64
  -

   Patch management:
   -

  Amazon Linux 2



Resolved in this release:

   -

   Packages were not marked as automatically installed by APT if you set
   security_only to true. When running the pe_patch::patch_server task with
   the security_only parameter set to true, packages were not marked as being
   automatically installed by APT. This caused problems if you rely on this
   marking for APT autoremove to remove old packages. The patch_server task
   now marks packages as automatically installed, regardless of the
   security_only parameter.
   -

   r10k can recover from typos in the config or Puppetfile. r10k now
   updates its cache repos when the remote URL changes. This allows r10k to
   recover from typos in the config or Puppetfile.
   -

   Couldn't complete restoration if the r10k_remote parameter wasn't set. The
   r10k_remote parameter wasn't set when restoring a backup with scope set to
   certs, code, or puppetdb. This prevented you from finishing restoration
   because the commands necessary to finish restoring your primary server did
   not print.
   -

   Schedule task button sometimes failed to redirect. When scheduling a
   task to run at some later time or interval, under some circumstances,
   clicking Schedule task did not redirect you to the Scheduled tasks page.
   -

   The fail_plan function didn't show custom error information. The
   fail_plan function ignored the kind and details parameters, which are used
   to specify custom, machine-parseable information about an error.
   -

   Scheduled jobs failed on FIPS installs. Scheduled jobs, including tasks
   and plans, couldn't run or be listed on FIPS installs of PE and resulted in
   the error javax.crypto.BadPaddingException.





Check out the release notes:
https://puppet.com/docs/pe/2021.5/release_notes_pe_index.html



Important note: If you are using Continuous Delivery for PE, upgrade to
CD4PE 4.8.2 or a newer version prior to upgrading to Puppet Enterprise
2021.5. We resolved a PuppetDB issue causing the generation of new fact
charts on the Nodes page to fail.



*Download PE 2021.5 here*:
https://puppet.com/try-puppet/puppet-enterprise/download/


As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKQkyrPFhJGnxnC%2BZyPR4%3DBOjr26u-NC5fUH3cBdtVQRA%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.26.0 is now available

[Puppet Product Updates]

The release contains new features, minor enhancements, and bug fixes
including:



Agent 6.26.0

   -

   Support for trusted facts with the puppet lookup command
   -

   Added support for Red Hat Enterprise Linux 9 Beta (x86_64)
   -

   Added support for Windows Server 2022(x86_64).



PuppetDB 6.20.0

   -

   Added an optimization to improve the performance of the inventory
   endpoint when filtering on a trusted fact.



Server 6.18.0

   -

   Users can now enable module metrics collection via Dropsonde. To turn
   this on, configure dropsonde: { enabled: true } in puppetserver.conf. By
   default when enabled, Dropsonde collects metrics when the service is
   started and once a week thereafter.





For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/6/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2Bm%2BZeM5F0o-RbFZuxeZPGHe5ZYTfmpPg8kSNo%2B%3D2OX7Mfw%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.14.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.14.0, is now available!



The release contains enhancements and vulnerability fixes, including:

Agent 7.14.0

   -

   Added support for trusted facts with the puppet lookup command
   -

   Added support for Red Hat Enterprise Linux 9 Beta (x86_64)


   -

   Upgraded Ruby component to 2.7.5.
   -



PuppetDB 7.9.0

   -

   Added support for Debian 11.I


   -

   Improved performance of the "deactivate node" command.
   -

   Improved performance of the fact-contents endpoint. Testing against a
   database of 10,000 mocked nodes, there was an observed 84% decrease in time
   taken to complete a difficult query.

Server 7.6.0

   -

   Puppet Server is now packaged for Debian 11. It requires Java 11 to be
   installed.



For the full list of changes, check out the release notes:



https://puppet.com/docs/puppet/7/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKaL3nJ8U-VbV5RWkWr_8wL%2Bs3nCMt-Eh%2BYxKT3kVcVqQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.26.0 is now available

[Puppet Product Updates]

The release contains new features, minor enhancements, and bug fixes
including:



Agent 6.26.0

   -

   Changed the priority of the --environment option by skipping the
   classification whenever the flag is specified. This allows the user to
   bypass the ENC enforced environment with the CLI option.
   -

   Added support for Red Hat Enterprise Linux (RHEL) 9.
   -

   Added support for Windows Server 2022(x86_64).



PuppetDB 6.20.0

   -

   Added an optimization to improve the performance of the inventory
   endpoint when filtering on a trusted fact.



Server 6.18.0

   -

   Users can now enable module metrics collection via Dropsonde. To turn
   this on, configure dropsonde: { enabled: true } in puppetserver.conf. By
   default when enabled, Dropsonde collects metrics when the service is
   started and once a week thereafter.




For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/6/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKrNEDngicYhyPfjLN0334n74xhb0xAuBvu7b_RvDyAmQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.14.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.14.0, is now available!



The release contains enhancements and vulnerability fixes, including:

Agent 7.14.0

   -

   Support for RHEL 9.


   -

   Upgraded Ruby component to 2.7.5.

Server 7.6.0

   -

   Puppet Server is now packaged for Debian 11. It requires Java 11 to be
   installed.


PuppetDB 7.9.0

   -

   Added support for Debian 11.I


   -

   Improved performance of the "deactivate node" command.
   -

   Improved performance of the fact-contents endpoint. Testing against a
   database of 10,000 mocked nodes, there was an observed 84% decrease in time
   taken to complete a difficult query.

For the full list of changes, check out the release notes:



https://puppet.com/docs/puppet/7/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABRr%2BmJZ7-vsCbJFxYBrShbpXhKPn-HWPK8N-Yv%2Bvk%3DSzVL7Dg%40mail.gmail.com.

[Puppet Users] Bolt 3.21.0 is now available

[Puppet Product Updates]

VERSION 3.21.0

*in this release*

✨  *new features*

   - Bolt now supports managing and applying configuration policies for
   targets. For more information about this feature, see the documentation
   

   .

VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pX5YYDJtS41JEK04HVTD_TPC-t14Z%3Dh93CtzqHUqi0WKA%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.13.1 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.13.1, is now available!



The release contains enhancements and fixes, including:

Agent 7.13.1

   -

   Support for Windows Server 2022
   -

   Support for trusted facts with the puppet lookup command
   -

   Reduced compiler memory usage

PuppetDB 7.8.0

   -

   PuppetDB should no longer delete the last day of reports a day earlier
   than specified by report-ttl in some cases.

Server 7.5.0

   -

   Puppet Server is now shipping with the Dropsonde
    gem, which collects metrics on
   users’ modules. Users can now enable automatic module metrics collection,
   as well as access the Dropsonde CLI via `puppetserver dropsonde`.
   -

   As of this release, we are no longer shipping packages for RHEL/Centos 6.

For the full list of changes, check out the release notes:



https://puppet.com/docs/puppet/7/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMUqtyR%3Dx0awzoCnohkpXtM4CdE-4zze8fLN5MT%2BnyRCAQ%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.9 is now available!

[Puppet Product Updates]

The latest patch release for the current Long Term Support (LTS) version of
Puppet Enterprise, 2019.8.9, is now available!



This is a backward-compatible release that contains enhancements and bug
fixes, including:



   -

   TLS v1.3 is enabled by default. PE is now compatible with TLSv1.2 and
   TLSv1.3 by default for both FIPS and non-FIPS installations. To update your
   protocol or ciphers, review the Configuring security settings
   
   docs. For a list of compatible ciphers, see the Ciphers reference
   

   .
   - This version of PE includes version 3 of the PE support script, which
   offers more options for modifying the support script’s behavior to meet
   your needs.
   -

   Agent support for:
   -

  Ubuntu 18.04 aarch64
  -

  Debian 11 (Bullseye) amd64
  -

  Red Hat Enterprise Linux 8 FIPS x86_64
  -

  AlmaLinux x86_64 for Enterprise Linux 8
  -

  Rocky Linux x86_64 for Enterprise Linux 8
  -

   Primary PE server support added for:
   -

  AlmaLinux 8
  -

  Rocky Linux 8
  -

   And so much more! Check out the full list of changes below.



For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html



Resolved in this release:



   -

   CVE-2021-27023 : A flaw
   was discovered in Puppet agent and Puppet Server that may result in a leak
   of HTTP credentials when following HTTP redirects to a different host. This
   is similar to CVE-2018-107
   .
   -

   CVE-2021-27025 : A flaw
   was discovered in Puppet agent where the agent may silently ignore Augeas
   settings or may be vulnerable to a Denial of Service condition prior to the
   first ‘pluginsync’.
   -

   CVE-2021-27026 : A flaw
   was discovered in Puppet Enterprise and other Puppet products where
   sensitive plan parameters may be logged.



Important note: If you are using Continuous Delivery for PE, upgrade to
CD4PE 4.8.2 prior to upgrading to Puppet Enterprise 2019.8.9. We resolved a
PuppetDB issue causing the generation of new fact charts on the Nodes page
to fail.



Download PE 2019.8.9 here:
https://puppet.com/misc/pe-files/previous-releases/



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMX_Gs%3D7cjC3CyAKFM7hjW2twgQfR8hL8js3BJerzP_N5g%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.4.0 is now available!

[Puppet Product Updates]

The latest release for the Puppet Enterprise release track, PE 2021.4.0, is
now available!



Enhancements in this release include:



   -

   TLS v1.3 is enabled by default. PE is now compatible with TLSv1.2 and
   TLSv1.3 by default for both FIPS and non-FIPS installations. To update your
   protocol or ciphers, review the Configuring security settings
   
   docs. For a list of compatible ciphers, see the Ciphers reference
   

   .
   - New RBAC /command endpoints. Several new /command endpoints in the
   RBAC API v1 allow you to use the API to make small changes to existing
   data. To see the list of newly added RBAC /command endpoints, check out
   the release notes
   

   .
   -

   This version of PE includes version 3 of the PE support script, which
   offers more options for modifying the support script’s behavior to meet
   your needs.
   -

   Agent support for:
   -

  Ubuntu 18.04 aarch64
  -

  Debian 11 (Bullseye) amd64
  -

  Red Hat Enterprise Linux 8 FIPS x86_64
  -

  AlmaLinux x86_64 for Enterprise Linux 8
  -

  Rocky Linux x86_64 for Enterprise Linux 8
  -

   Primary PE server support added for:
   -

  AlmaLinux 8
  -

  Rocky Linux 8
  -

   And so much more! Check out the full list of changes below.


For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/latest/release_notes_pe_index.html



Resolved in this release:



   -

   CVE-2021-27023 : A flaw
   was discovered in Puppet agent and Puppet Server that may result in a leak
   of HTTP credentials when following HTTP redirects to a different host. This
   is similar to CVE-2018-107
   .
   - CVE-2021-27025 : A
   flaw was discovered in Puppet agent where the agent may silently ignore
   Augeas settings or may be vulnerable to a Denial of Service condition prior
   to the first ‘pluginsync’.
   -

   CVE-2021-27026 : A flaw
   was discovered in Puppet Enterprise and other Puppet products where
   sensitive plan parameters may be logged.



Important note: If you are using Continuous Delivery for PE, upgrade to
CD4PE 4.8.2 or a newer version prior to upgrading to Puppet Enterprise
2021.4. We resolved a PuppetDB issue causing the generation of new fact
charts on the Nodes page to fail.



Download PE 2021.4 here:
https://puppet.com/try-puppet/puppet-enterprise/download/


As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMWurSZzFa1NuEsqhXTSV4FYx9g0cnDhT9i4omNmK8x3QA%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.25.1 is now available

[Puppet Product Updates]

The next release in the Puppet 6 series, Puppet 6.25.1, is now available!



The release contains enhancements and vulnerability fixes, including:

   -

   Faster iterative functions, including reduce and merge.
   -

   CVE-2021-27023  - A flaw
   was discovered in Puppet Agent and Puppet Server that may result in a leak
   of HTTP credentials when following HTTP redirects to a different host. This
   is similar to CVE-2018-107
   .
   -

   CVE-2021-27025  - A flaw
   was discovered in Puppet Agent where the agent may silently ignore Augeas
   settings or may be vulnerable to a Denial of Service condition prior to the
   first `pluginsync`.
   -

  Note that if you upgrade agents to Puppet 6.25.1, you must first
  upgrade PuppetDB to 6.19.1, otherwise catalog storage does not work.

For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/6/release_notes_osp.html


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMURsqjGAiY5Rx51SSuJLbvw35hQ%3Do-%3Dyts9RT1j6e_emQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.12.1 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.12.1, is now available!

The release contains vulnerability fixes, including:

   -

   CVE-2021-27023  - A flaw
   was discovered in Puppet Agent and Puppet Server that may result in a leak
   of HTTP credentials when following HTTP redirects to a different host. This
   is similar to CVE-2018-107
   .
   -

   CVE-2021-27025  - A flaw
   was discovered in Puppet Agent where the agent may silently ignore Augeas
   settings or may be vulnerable to a Denial of Service condition prior to the
   first `pluginsync`.
   -

  Note that if you upgrade agents to Puppet 7.12.1, you must first
  upgrade PuppetDB to 7.7.1, otherwise catalog storage does not work.

For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMUseUkmgftSnnzf7ca71XJky4FuPoB5zGQPG15Hb47_tQ%40mail.gmail.com.

[Puppet Users] Bolt 3.20.0 is now available

[Puppet Product Updates]

VERSION 3.20.0

*in this release*

✨  *new features*

   - The interpreters transport configuration option now accepts both array
   and string values, allowing you to pass options to the interpreter as well
   as the path to an executable. For more information about this configuration
   option, see the transport configuration reference
   .

🔧  *bug fixes*

   - Bolt now only resolves configuration for the PuppetDB client as
   needed. Previously, Bolt resolved this configuration for every command,
   which could cause Bolt to error when it shouldn't.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pWHE3ZDDmE4-rHtmZ-GG5Nb--VXiRS_9C46h1N-q-XyDA%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.12.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.12.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



Agent 7.12.0

   -

   Support for Rocky 8 (x86_64) and AlmaLinux 8 (x86_64)
   -

   Improved compiler memory allocation
   -

   Faster iterative functions, including reduce and merge
   -

   A fixed regression when running on Windows 8.3 paths introduced in 7.9.0



PuppetDB 7.7.0

   -

   Added an optimization to improve the performance of the inventory
   endpoint when filtering on a trusted fact



For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMV2_qe87Q0%2BaCUV0CFnLwH0mzsvnQ491wUG%3D7G3CFRQ3g%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.25.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 6 series, Puppet 6.25.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



Agent 6.25.0

   -

   Support for Rocky 8 (x86_64), AlmaLinux 8 (x86_64), and Ubuntu 18.04
   (aarch64)
   -

   Improved compiler memory allocation
   -

   Several environment convergence improvements



Server 6.17.0

   -

   TLS v1.3 is enabled by default
   -

   The CA no longer produces duplicate CRL entries when revoking already
   revoked certificates.
   -

   The CA command line tool can purge duplicates from existing CRLs.



PuppetDB 6.19.0

   -

   Added an optimization to improve the performance of the inventory
   endpoint when filtering on a trusted fact.



For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/6/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMX_vUxDVPkLfNPALGH_bK%2BoAoPDJHrGENc7HfQBhZu-AQ%40mail.gmail.com.

[Puppet Users] Bolt 3.19.0 is now available

[Puppet Product Updates]

VERSION 3.19.0

*in this release*

✨  *new features*

   - Bolt packages are now available for Debian 11.
   - The following bundled modules have been updated to their latest
   versions:
  - augeas_core 1.2.0
  
  - cron_core 1.1.0
  
  - host_core 1.1.0
  
  - mount_core 1.1.0
  
  - selinux_core 1.2.0
  
  - sshkeys_core 2.3.0
  
  - stdlib 8.1.0
  
  - yumrepo_core 1.1.0
  
  - zfs_core 1.3.0
  

🔧  *bug fixes*

   - Bolt now correctly resolves plugins used under the
   inventory-config setting in bolt-defaults.yaml. Previously, Bolt would
   error with an "undefined method" message when using plugins under this
   setting.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pVGHk_FSJXxVvaevQhvBDzCYaM34LOoGR4-Ss3xxE4k3g%40mail.gmail.com.

[Puppet Users] Removal of CentOS 8 Support

[Puppet Product Updates]

Hello all,

This is an announcement that we’ll be removing support for CentOS 8 in
February 2022 because CentOS 8 is EOLed from the vendor in December 2021.
For a list of other supported operating systems for your primary server,
see the supported operating systems

docs.

This removal is in accordance with our platform support lifecycle policy,
which can be found on our website here:
https://puppet.com/docs/puppet-enterprise/platform-support-lifecycle/

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMW%2BiKpvqq%3DO76M1Do0KthBmFAJ1Je7yqpb98uYc7wEC-g%40mail.gmail.com.

[Puppet Users] Bolt 3.18.0 is now available

[Puppet Product Updates]

VERSION 3.18.0

*in this release*

✨  *new features*

   - Bolt now respects the interpreters configuration option when running
   scripts, allowing you to specify a path to an interpreter. To enable this
   feature, set the future.script_interpreter option in your project
   configuration. For more information, see the
   bolt-project.yaml reference
   .
   - The bolt project init and New-BoltProject commands now create a
   .gitignore file with local Bolt files, simplifying the process of
   excluding user-specific files from your project repositories.
   - You can now provide an authorization token to the Forge when
   installing modules with Bolt using the new configuration option
   module-install.forge.authorization_token. For more information, see the
   documentation
   

   .
   - Bolt now supports loading scripts from a project's or module's scripts/
   directory by default when using a Puppet file reference (
   /scripts/). For more information about this change, see the
   developer update
   

   .
   - Bolt now ships with the latest versions of each of its bundled
   modules, including:


   -

   package 2.1.0
   


   -

   puppet_agent 4.9.0
   


   -

   puppet_conf 1.2.0
   


   -

   reboot 4.1.0 


   -

   service 2.1.0
   


   -

   stdlib 8.0.0 

🔧  *bug fixes*

   - Bolt now returns exit code 1 when an operation fails. Previously, Bolt
   returned exit code 2.
   - BoltSpec's allow_script, expect_script, allow_upload, and expect_upload
   functions now support absolute paths. Previously, only relative paths or
   Puppet file references were supported.
   - Bolt now correctly sets the main plan's ID during a plan run.
   Previously, Bolt was setting the main plan's ID incorrectly, causing Bolt
   to log some warnings when it should not have.
   - Bolt now supports using the scripts mount in Puppet manifests.
   Previously, the scripts mount was not supported.

🚨  *deprecations*

   - The future.file_paths configuration option is deprecated. Bolt no
   longer honors this setting and will look for scripts in a project's or
   module's scripts/ directory by default.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pWCOvy-OobqgwsYOWr-ukGdM6Xix7RdFBZU19oDnbkqyw%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.11.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.11.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



   -

   Adding the write_catalog_summary setting to control whether the
   resources.txt and classes.txt files are written to disk after applying a
   catalog
   -

   Adding support for Ubuntu 18.04 aarch64
   -

   Adding support for multiple Facter implementations
   -

   The agent now saves a local copy of its last run report, even if it
   fails to submit the report to the primary Puppet server.
   -

   Puppet Server and PuppetDB now support TLS 1.3 and associated cipher
   suites by default.


For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMVk_Rn8S7C-vvrGh_USfDkPE55KTxQUyUqs9WjQyV2zMg%40mail.gmail.com.

[Puppet Users] Removal of EL 6 Support from Puppet Platform 7.x

[Puppet Product Updates]

Hello all,

This is a general announcement that we will be removing EL 6 support in
Puppet Platform 7.14 in December 2021. This date and version number is
subject to change, but removal of EL 6 support will not happen earlier.

This is in accordance with our platform support lifecycle policy, which can
be found on our website here:
https://puppet.com/docs/puppet-enterprise/platform-support-lifecycle/

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMXqy1jeKU9MOrAngrRKPL-pucCdJrwpzXsE1zpFgoDKiQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.10.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.10.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



   -

   The Windows MSI installer has the option to enable long filename support
   -

   New settings for controlling fact limits: fact name length, fact value
   length, number of facts, payload size
   -

   Removed support for  Fedora 30 (x86_64),  Fedora 31 (x86_64), MacOSX
   10.14 (x86_64)
   -

   The CA has received two improvements in this release; a new cli action
   pruning duplicate entries in the CRL, and faster CRL reads for the server
   to decrease possible timeouts from reading the CRL.


For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMVunKs6Q5MYehHn7j7BpThAVkQCCOeJWzZDjFP9SXbkJw%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.24.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 6 series, Puppet 6.24.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



   -

   support for Debian 11 Bullseye amd64
   -

   code-signed MacOS executable files for `puppet` and `pxp-agent`
   -

   `exec` provider directly executes commands when passed as an array
   (instead of executing via the standard shell)



For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMUD7UwB1iwTL8e_8T6DUHZBhqw%3DaQbZr9VFohSrkPs9%3DQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.9.0 is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.9.0, is now available!



The release contains new features, minor enhancements, and bug fixes
including:



   -

   installing `.exe` packages on Windows using HTTPS as a package source
   -

   support for Debian 11 Bullseye amd64
   -

   code-signed MacOS executable files for `puppet` and `pxp-agent`
   -

   `exec` provider directly executes commands when passed as an array
   (instead of executing via the standard shell)


For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMU-tX9uNAExAD0yfLubDJ7M_HJwnQ8Q5cn2MiVCMuZqtA%40mail.gmail.com.

[Puppet Users] Bolt 3.13.0 is now available

[Puppet Product Updates]

VERSION 3.13.0

*in this release*

✨  *new features*

   - Plans can now print messages that only appear when running in verbose
   mode using the new out::verbose plan function. For more information
   about this function, see the reference documentation
   .
   - You can now log messages from a plan directly to Bolt's log levels
   using the new built-in log modules. The new functions include
   log::trace, log::debug, log::info, log::warn, log::error, and log::fatal.
   For more information about these functions, see the documentation
   .
   - Bolt now ships packages for Fedora 34.


VIEW FULL RELEASE NOTES


*in the works*

   - Improvements to the wait() plan function.
   - A verbose step for YAML plans.
   - Support for clearing the plan and task caches.
   - Printing messages from plans to Bolt's logs.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

July's highlighted feature is: *BoltSpec*!

*What is BoltSpec?*

BoltSpec is a library of helpers that ships with Bolt. It is intended to be
used with RSpec, a testing tool, to write unit tests for your plans.
Specifically, BoltSpec's helpers let you test the behavior of your plans
without the need to connect to targets.


*Why should I use BoltSpec?*

Because plans can include complex logic that automates different jobs, it's
important to test that the plan behaves as you expect. BoltSpec lets you
easily write tests for your plans so you can test their behavior in
development and catch any errors before your plans are used in production.
Also, because BoltSpec stubs out Bolt functions that connect to targets,
you don't need to worry about provisioning containers or VMs to run these
tests.


*How do I use BoltSpec?*

Using BoltSpec is as easy as installing and configuring rspec-puppet for
your module or project, and then adding a couple lines to your tests'
configuration file. If you already develop Puppet modules using the Puppet
Development Kit (PDK), then most of this is already done for you.

Going over all the details of using BoltSpec to test your plans is a little
much for an email. So if you're interested in testing your plans, why not
check out our new Testing Plans
 documentation?

VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pX-V4au5Vqo4S2KVg1sWOeUw4fa8z9RhXr%2B3OsxQtZMKA%40mail.gmail.com.

[Puppet Users] Bolt 3.12.0 is now available

[Puppet Product Updates]

VERSION 3.12.0

*in this release*

✨  *new features*

   - The puppet_agent::install task now supports installing the puppet-agent
   package on macOS 11 targets.
   - You can now silence warnings about exported resources not being
   supported in apply blocks by including the exported_resources ID under
   the disable-warnings configuration option. For more information about
   this setting, see the reference documentation
   

   .

🔧  *bug fixes*

   - Bolt no longer errors when showing plans or tasks when the plan or
   task cache includes a module that has been moved or deleted.


VIEW FULL RELEASE NOTES


*in the works*

   - A new plan function for printing messages in verbose mode.
   - New built-in plan functions for logging messages at Bolt's log levels.

   - Improvements to the wait() plan function.
   - Fedora 34 packages.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

July's highlighted feature is: *BoltSpec*!

*What is BoltSpec?*

BoltSpec is a library of helpers that ships with Bolt. It is intended to be
used with RSpec, a testing tool, to write unit tests for your plans.
Specifically, BoltSpec's helpers let you test the behavior of your plans
without the need to connect to targets.


*Why should I use BoltSpec?*

Because plans can include complex logic that automates different jobs, it's
important to test that the plan behaves as you expect. BoltSpec lets you
easily write tests for your plans so you can test their behavior in
development and catch any errors before your plans are used in production.
Also, because BoltSpec stubs out Bolt functions that connect to targets,
you don't need to worry about provisioning containers or VMs to run these
tests.


*How do I use BoltSpec?*

Using BoltSpec is as easy as installing and configuring rspec-puppet for
your module or project, and then adding a couple lines to your tests'
configuration file. If you already develop Puppet modules using the Puppet
Development Kit (PDK), then most of this is already done for you.

Going over all the details of using BoltSpec to test your plans is a little
much for an email. So if you're interested in testing your plans, why not
check out our new Testing Plans
 documentation?


VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUZS%2B_zBHO%2BqVRyWVPtjSYHUg8tBJ%3DOz3kYB_8YUD%2B6bA%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.7 is now available!

[Puppet Product Updates]

The latest patch release for the current Long Term Support (LTS) version of
Puppet Enterprise, 2019.8.7, is now available!



This is a backward-compatible release that contains enhancements and bug
fixes, including:



   -

   Fixed an issue where someone with the ability to query PuppetDB could
   arbitrarily write, update, or delete data in Postgres. CVE-2021-27021
   
   -

   Agent support for macOS 11, Red Hat Enterprise Linux 8 ppc64le, and
   Ubuntu 20.04 aarch64
   -

   Export task node data results from task runs to a CSV file
   -

   Update your CRLs using the new API endpoint: certificate_revocation_list



For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html



Download PE 2019.8.7 here:
https://puppet.com/misc/pe-files/previous-releases/



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGFKYV_yU_TAdj4emD_RiA6YgTBtjNd2y_9HxUYN%3DMSZB%2B%3Dt1Q%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.2 is now available!

[Puppet Product Updates]

The latest release for the Puppet Enterprise release track, PE 2021.2 is
now available!



New features and enhancements in this release include:

   -

   Fixed an issue where someone with the ability to query PuppetDB could
   arbitrarily write, update, or delete data in Postgres. CVE-2021-27021
   
   -

   Agent support for macOS 11, Red Hat Enterprise Linux 8 ppc64le, and
   Ubuntu 20.04 aarch64
   -

   Export task node data results from task runs to a CSV file
   -

   Update your CRLs using the new API endpoint: certificate_revocation_list


For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/latest/release_notes_pe_index.html





Download PE 2021.2 here:
https://puppet.com/try-puppet/puppet-enterprise/download/


As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGFKYV-2wK120YaT%2B0xT_DYnxEJY23xBTW1qnQqP6j9d5iO6Hg%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.8.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.8.0, is now available!

Highlights from the 7.8.0 release include:

   -

   Fixed an issue where someone with the ability to query PuppetDB could
   arbitrarily write, update, or delete data in Postgres. CVE-2021-27021
   
   -

   The Puppet agent now supports long filenames on Windows! This means that
   the DSC modules will all work properly and you can manage files with paths
   longer than 260 characters. You will need to enable long path support on
   each Windows agent via a registry key
   

   (hint: use the puppetlabs-registry
    module for that!)
   -

   The Puppetserver CA now enables you to manage its certificate revocation
   list via a new API endpoint. This makes it easier to manage when you have a
   volatile infrastructure and you need to update the CRL often.
   -

   We've made several improvements to our macOS support, including user
   management and user keychain access.
   -

   Puppet now supports Fedora 34. Experimental Ruby 3 support has been
   improved and we now CI test all pull requests to the Puppet repository
   against Ruby 3.


For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGFKYV9nGM_GWpGeWyPXWd9yuOMAU8ghT2W27OTCb2deN97%2BbQ%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.23.0 is now available

[Puppet Product Updates]

The next release in the Puppet 6 series, Puppet 6.23.0, is now available!

Highlights from the 6.23.0 release include:

   -

   Fixed an issue where someone with the ability to query PuppetDB could
   arbitrarily write, update, or delete data in Postgres. CVE-2021-27021
   
   -

   The Puppet agent now supports long filenames on Windows! This means that
   the DSC modules will all work properly and you can manage files with paths
   longer than 260 characters. You will need to enable long path support on
   each Windows agent via a registry key
   

   (hint: use the puppetlabs-registry
    module for that!)
   -

   Ruby performance patches have landed, meaning that loading Puppet and
   Facter will now spend 50-90% less time on filesystem IO operations.
   -

   The Puppetserver CA now enables you to manage its certificate revocation
   list via a new API endpoint. This makes it easier to manage when you have a
   volatile infrastructure and you need to update the CRL often.
   -

   Puppet now supports macOS 11 (Big Sur).


For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGFKYV_qpedoQ9YCBadmwiH59iNS%3DZKi69hcUT%3D5NkPUhODx1A%40mail.gmail.com.

[Puppet Users] Removal of EL 5, Fedora 30/31 and macOS 10.14 support

[Puppet Product Updates]

Hello all,

This is a general announcement that we will be removing EL 5, Fedora 30/31
and macOS 10.14 support in an upcoming Puppet Platform 6 series release, as
well as Fedora 30/31 and macOS 10.14 support in an upcoming Puppet Platform
7 series release.

This is in accordance with our platform support lifecycle policy, which can
be found on our website here:
https://puppet.com/docs/puppet-enterprise/platform-support-lifecycle/


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAAzN9J9r6tMOTAK2TAUERa_4go3rrTMX2G2Nvby4%3DQUnOxXN9Q%40mail.gmail.com.

[Puppet Users] Bolt 3.11.0 is now available

[Puppet Product Updates]

VERSION 3.11.0

*in this release*

✨  *new features*

   - Bolt now ships packages for macOS 11 (Big Sur).
   - Bolt now ships with Puppet 7.7.0.
   - Several of Bolt's bundled modules have been updated to their latest
   versions:


   -

   pkcs7 0.1.2 


   -

   puppet_agent 4.7.0
   


   -

   scheduled_task 3.0.1
   


   -

   stdlib 7.1.0 


🔧  *bug fixes*

   - Bolt no longer errors when printing command or script results that
   include an error but no output. Previously, Bolt would error with an
   'undefined method' message.
   - Bolt no longer errors when printing command or script results when
   using the pcp transport. Previously, Bolt would error with an 'undefined
   method' message.
   - The Bolt gem no longer errors when installing modules. Previously,
   Bolt would error with a 'missing parameter' message.


VIEW FULL RELEASE NOTES


*in the works*

   - More readable type errors when running plans.
   - Support for waiting on all remaining backgrounded tasks using the
   wait() plan function.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

June's highlighted feature is: *streaming*!

*What is streaming?*

Don't worry, the Bolt team isn't releasing *yet another* streaming service.
When you run commands and scripts on targets, Bolt gives you the option of
streaming the output from these commands and scripts as they are executed
on the targets. This lets you see what is happening on every target you run
the action on in near real-time, making it easier to debug problems with
commands and scripts or to see where in the process of executing an action
the target is.


*How do I enable streaming?*

There are two ways to enable streaming in Bolt. You can either enable it
from the command line for a single run with the --stream command-line
option, or you can enable it permanently in your configuration with the
stream setting. Whenever Bolt streams output, it will print output from
stdout and stderr in the order it receives it from each target, and will
prepend each line with the name of the target that it came from.


To learn more about streaming, check out the documentation below.


VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pVMrLZkNut5T2jwi1vGigtevFpR-PEX63A%2BqA5w9r_XOg%40mail.gmail.com.

[Puppet Users] Bolt 3.10.0 is now available

[Puppet Product Updates]

VERSION 3.10.0

*in this release*

✨  *new features*

   - You can now view which plugins are available to your project
using the bolt
   plugin show command and Get-BoltPlugin PowerShell cmdlet.
   - You can now look up values under Hiera's plan_hierarchy key from the
   CLI using the bolt lookup --plan-hierarchy command or Invoke-BoltLookup
   -PlanHierarchy PowerShell cmdlet. For more information, see the
   documentation
   .

   - Need to interpolate variables into your Hiera lookups on the command
   line? You can now pass variables to the lookup command using
   variable=value syntax. For more information, see the documentation
   .
   - Bolt packages on *nix platforms now ship with a bash autocompletion
   script. The script is saved to /etc/bash_completion.d/ when the Bolt
   package is installed.

🔧  *bug fixes*

   - BoltSpec now supports testing plans that invoke the parallelize() plan
   function. Previously, testing these plans caused Bolt to error.
   - The PuppetBolt PowerShell module now correctly passes remaining
   arguments to the -Arguments parameter for the
   Invoke-BoltScript cmdlet. Previously, the PowerShell parser would error
   if any remaining arguments were provided.

🚨  *deprecations*

   - The PuppetBolt PowerShell module will no longer ship with Bolt
   packages on Windows in a future release. The PuppetBolt PowerShell module
   can now be installed from the PowerShell Gallery
    instead.


VIEW FULL RELEASE NOTES


*in the works*

   - Packages for macOS 11.
   - More readable type errors when running plans.
   - Support for waiting on all remaining backgrounded tasks using the
   wait() plan function.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

June's highlighted feature is: *streaming*!

*What is streaming?*

Don't worry, the Bolt team isn't releasing *yet another* streaming service.
When you run commands and scripts on targets, Bolt gives you the option of
streaming the output from these commands and scripts as they are executed
on the targets. This lets you see what is happening on every target you run
the action on in near real-time, making it easier to debug problems with
commands and scripts or to see where in the process of executing an action
the target is.


*How do I enable streaming?*

There are two ways to enable streaming in Bolt. You can either enable it
from the command line for a single run with the --stream command-line
option, or you can enable it permanently in your configuration with the
stream setting. Whenever Bolt streams output, it will print output from
stdout and stderr in the order it receives it from each target, and will
prepend each line with the name of the target that it came from.


To learn more about streaming, check out the documentation below!

VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUkgoHq0yhW9V4caysv9vA87_RVUCVmVKT78ubyfEdMjA%40mail.gmail.com.

[Puppet Users] Bolt 3.9.2 is now available

[Puppet Product Updates]

VERSION 3.9.2

🔧  *bug fixes*

   - Bolt no longer errors when using the --run-as command-line option on a
   Windows controller.

VIEW FULL RELEASE NOTES


*in the works*

   - Support for looking up values under the Hiera plan_hierarchy key from
   the command line.
   - Shipping Bolt with a bash autocompletion script.
   - Packages for macOS 11.
   - More readable type errors when running plans.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

May's highlighted feature is: *streaming*!

*What is streaming?*

Don't worry, the Bolt team isn't releasing *yet another* streaming service.
When you run commands and scripts on targets, Bolt gives you the option of
streaming the output from these commands and scripts as they are executed
on the targets. This lets you see what is happening on every target you run
the action on in near real-time, making it easier to debug problems with
commands and scripts or to see where in the process of executing an action
the target is.


*How do I enable streaming?*

There are two ways to enable streaming in Bolt. You can either enable it
from the command line for a single run with the --stream command-line
option, or you can enable it permanently in your configuration with the
stream setting. Whenever Bolt streams output, it will print output from
stdout and stderr in the order it receives it from each target, and will
prepend each line with the name of the target that it came from.


To learn more about streaming, check out the documentation below!

VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUuKEu6VQsp5W2TaJ5kLP%3DVtOYtMbvQK89hgrY-f85Cig%40mail.gmail.com.

[Puppet Users] Bolt 3.9.1 is now available

[Puppet Product Updates]

VERSION 3.9.1

*in this release*

✨  *new features*

   - The PuppetBolt PowerShell module now ships to the PowerShell Gallery
   . New versions of
   the PuppetBolt module are shipped at the same time as Bolt packages.

🔧  *bug fixes*

   - The BoltSpec::Run.download_file function no longer errors with an
   'undefined method' message.
   - Bolt no longer errors when executing a parallelize or background block
   when the block references a variable from the parent scope is explicitly
   set to undef.

📈  *analytics*

   - Bolt reports whether or not a task is run in no-operation mode when it
   submits analytics. The value collected is true or false and does not
   include identifying information about the task.


VIEW FULL RELEASE NOTES


*in the works*

   - Support for looking up values under the Hiera plan_hierarchy key from
   the command line.
   - Shipping Bolt with a bash autocompletion script.
   - Packages for macOS 11.
   - More readable type errors when running plans.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

May's highlighted feature is: *streaming*!

*What is streaming?*

Don't worry, the Bolt team isn't releasing *yet another* streaming service.
When you run commands and scripts on targets, Bolt gives you the option of
streaming the output from these commands and scripts as they are executed
on the targets. This lets you see what is happening on every target you run
the action on in near real-time, making it easier to debug problems with
commands and scripts or to see where in the process of executing an action
the target is.


*How do I enable streaming?*

There are two ways to enable streaming in Bolt. You can either enable it
from the command line for a single run with the --stream command-line
option, or you can enable it permanently in your configuration with the
stream setting. Whenever Bolt streams output, it will print output from
stdout and stderr in the order it receives it from each target, and will
prepend each line with the name of the target that it came from.


To learn more about streaming, check out the documentation below!

VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUxJZsDnm_Qyn5cQwz2%2BiR_2%2B9FKTRRx4Sq89-D5U6Fzw%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.7.0 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet  7.7.0, is now available!

The release contains bug fixes and minor enhancements including:

   -

   Enhancements:
   -

  Puppet loads internal files using the require_relative method
  -

  Case sensitive parameter for the fqdn_rand() function
  -

  File limit with the max_files parameter
  -

  Improved Ruby performance
  -

  Added agent support for macOS Big Sur (11) and RedHat 8 on IBM Power
  -

   Resolution of the following issues:
   -

  Ruby 3 freezes CHILD_STATUS and cannot be stubbed
  -

  Agent failures with server_list
  -

  Puppet does not specify SELinux filetype when getting the default
  context
  -

  Unable to mask a static systemd service
  -

  Unable to update UserRightAssignment
  -

  PUPPET_SERVER MSI install property does not work

For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFH7jMV0gaH5i3W6Rgh30an%2BSnpYHad6EW3OG-EbPSDDbUqZNQ%40mail.gmail.com.

[Puppet Users] Bolt 3.9.0 is now available

[Puppet Product Updates]

VERSION 3.9.0

*in this release*

✨  *new features*

   - Plans now support fire-and-forget parallelism with the background()
   and wait() plan functions. For more information about using these new
   functions, see the documentation .
   - The docker, lxd, and podman transports now support the run-as
   configuration option, as well as all other privilege escalation options.
   For a detailed list of configuration options available to these transports,
   see the reference page
   .

🔧  *bug fixes*

   - Project plugin files are now uploaded to the correct directory when
   running the apply_prep and apply functions. Previously, these files were
   uploaded to the wrong directory, causing plans to fail if they referenced
   project files using Puppet file syntax (
   puppet:///modules//).
   - Setting the docker.service-url configuration option now correctly sets
   the DOCKER_HOST environment variable. Previously, this environment
   variable was not set, preventing connections to remote Docker hosts.

VIEW FULL RELEASE NOTES


*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

May's highlighted feature is: *scripts*!

*What is a script?*

A script is a list of commands that are executed by a certain program or
scripting engine. Scripts may be used to automate processes. Script files
are usually just text documents that contain instructions written in a
certain scripting language. When opened by the appropriate scripting
engine, the commands within the script are executed.

Bolt can execute scripts either on the command line or from a Bolt plan
using the run_script() function.


*How is a script different from a task?*

Bolt tasks are similar to scripts, but they are kept in modules and
optionally have a defined API for input into the task and output from the
task. This allows you to reuse and share them, and interact with them
programmatically more easily. Using the API capabilities of tasks requires
adding a JSON metadata file next to the task, which oftentimes is
unnecessary work for users who simply want to run a script.

VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pVjKZaVMgDverTnuUwcHftUuOOD0-opcr0MJyPVSYy7fg%40mail.gmail.com.

[Puppet Users] Bolt 3.8.1 is now available

[Puppet Product Updates]

VERSION 3.8.1

*in this release*

🔧  *bug fixes*

   - The apply_prep plan function now supports the _run_as option. To learn
   more about this plan function, see the plan functions reference page
   .
   - Bolt no longer stack traces when the controller does not have a home
   directory. Previously, Bolt would stack trace when running bolt help or bolt
   --help for the first time if there was no home directory for the
   logged-in user.
   - The file::exists, file::read, and file::readable plan functions no
   longer error when invoked outside of apply blocks when the future
   configuration option is not set.

📚 *documentation*

   - Bolt's JSON format is now documented. Check it out here
   .


VIEW FULL RELEASE NOTES


*in the works*

   - Improvements to parallelism in plans, including new background and wait
   functions.
   - Support for running plans in no-operation mode.
   - Support for looking up Hiera data using the plan_hierarchy key with
   the bolt lookup command.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

May's highlighted feature is: *scripts*!

*What is a script?*

A script is a list of commands that are executed by a certain program or
scripting engine. Scripts may be used to automate processes. Script files
are usually just text documents that contain instructions written in a
certain scripting language. When opened by the appropriate scripting
engine, the commands within the script are executed.

Bolt can execute scripts either on the command line or from a Bolt plan
using the run_script() function.


*How is a script different from a task?*

Bolt tasks are similar to scripts, but they are kept in modules and
optionally have a defined API for input into the task and output from the
task. This allows you to reuse and share them, and interact with them
programmatically more easily. Using the API capabilities of tasks requires
adding a JSON metadata file next to the task, which oftentimes is
unnecessary work for users who simply want to run a script.
VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pXL4cq2_J_urbArqHfAb_XD2LyhSucRdEddV3E-UXXpLQ%40mail.gmail.com.

[Puppet Users] Removal of Debian 8 support

[Puppet Product Updates]

Hello all,

This is a general announcement that we will be removing Debian 8 support
(all architectures) from the next Puppet Platform 6 series release, as well
as PuppetDB and Puppet Server Debian 8 support in the Puppet Platform 7
series release.

This is in accordance with our platform support lifecycle policy, which can
be found on our website here:
https://puppet.com/docs/puppet-enterprise/platform-support-lifecycle/


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAAzN9J9HdS4W3Rd%3D_siMKGJnFpCTwcx1a6m580q_Zsmvc%3D3wKw%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.6 is now available!

[Puppet Product Updates]

The latest patch release for the current Long Term Support (LTS) version of
Puppet Enterprise, 2019.8.6, is now available!



This is a backward-compatible release that contains enhancements and bug
fixes, including:



   -

   Customizable defaults of time freed for value reporting.
   -

   A new `crl_refresh_interval` parameter which updates agents’ CRL on a
   specified interval.



For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html



Download PE 2019.8.6 here:
https://puppet.com/misc/pe-files/previous-releases/



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGFKYV_PmGqdd4tSoZYCaJXyxTXagrG4yPTC-AwiDNHtLWRxBQ%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.1 is now available!

[Puppet Product Updates]

The latest release for the Puppet Enterprise release track, PE 2021.1 is
now available!



New features and enhancements in this release include:

   -

   Opt-in password complexity requirements for more secure access to PE.
   -

   Customizable defaults of time freed for value reporting.
   -

   Customizable banner for console login page.
   -

   A new `crl_refresh_interval` parameter which updates agents’ CRL on a
   specified interval.


For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/latest/release_notes_pe_index.html



Deprecations

Support for these agent platforms are deprecated in the PE 2021 release
stream:

   -

   Enterprise Linux 5
   -

   Enterprise Linux 7 ppc64le
   -

   SUSE Linux Enterprise Server 11
   -

   SUSE Linux Enterprise Server 12 ppc64le
   -

   Ubuntu 16.04 ppc64le
   -

   Debian 8
   -

   Solaris 10
   -

   Microsoft Windows 7, 8.1
   -

   Microsoft Windows Server 2008, 2008 R2



Reminder: Whitelist and blacklist were deprecated in a previous release in
favor of allowlist and blocklist. Classes, parameters, and file names that
use these terms continue to work, but we recommend updating your
classification, Hiera data, and pe.conf files as soon as possible in
preparation for their removal in a future release.



Download PE 2021.1 here:
https://puppet.com/try-puppet/puppet-enterprise/download/


As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGFKYV8UkrkgK5gYrziepQyENeXEuUG6AY4sx7sDWULasEHLRw%40mail.gmail.com.

[Puppet Users] Bolt 3.8.0 is now available

[Puppet Product Updates]

VERSION 3.8.0

*in this release*

✨  *new features*

   - The puppet_agent::facts_diff task has a new exclude parameter which
   can be used to exclude specific facts from the diff. For more information
   about this task, see the module documentation
    on the
   Puppet Forge.
   - You can now look up values in Hiera from the Bolt command line using
   the new bolt lookup shell command and Invoke-BoltLookup Powershell
   cmdlet. Lookups are performed in the context of a target, and Bolt
   automatically collects a target's facts before looking up a value. For more
   information about using this command, see the documentation
   

   .
   - Bolt now supports loading files and scripts using their fully
   qualified names. This behavior is opt-in only and is the first phase in a
   multi-phase process of moving Bolt towards using fully qualified names for
   files and scripts. For more information about this change, how it will be
   phased in over time, and how to opt-in to the new behavior, see the
developer
   update
   

   .

🚨  *removals*

   - The puppet5 collection is no longer available to the
   puppet_agent::install task, as Puppet 5 has reached end of life.


VIEW FULL RELEASE NOTES


*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

May's highlighted feature is: *scripts*!

*What is a script?*

A script is a list of commands that are executed by a certain program or
scripting engine. Scripts may be used to automate processes. Script files
are usually just text documents that contain instructions written in a
certain scripting language. When opened by the appropriate scripting
engine, the commands within the script are executed.

Bolt can execute scripts either on the command line or from a Bolt plan
using the run_script() function.


*How is a script different from a task?*

Bolt tasks are similar to scripts, but they are kept in modules and
optionally have a defined API for input into the task and output from the
task. This allows you to reuse and share them, and interact with them
programmatically more easily. Using the API capabilities of tasks requires
adding a JSON metadata file next to the task, which oftentimes is
unnecessary work for users who simply want to run a script.

VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pXsSGzBWNmFcCqg%3D-Z%3DgQ-p0VbMiKxsxqb83eN7d1x%2Bxg%40mail.gmail.com.

[Puppet Users] Puppet Platform 6.22.1 is now available

[Puppet Product Updates]

The next release in the Puppet 6 series, Puppet 6.22.1, is now available!

The release contains bug fixes and minor improvements, including:

   - This release makes the following improvements to the puppet facts diff
   CLI command:
  - The command shows all of the differences between Facter 3 and
  Facter 4 — including facts only available in Facter 4 — and sorts the
  output results in alphabetical order. You can also remove certain facts
  from the output using the --exclude  CLI option and see
the results
  in a fully structured form.
  - The command filters the output based on an exclude list. This only
  contains volatile facts — those that are expected to change value between
  consecutive Facter runs.
  - The command pretty-prints JSON output. You can specify the older
  form with --render_as json.
   - This release bumps Curl to 7.76.0, fixing the following CVEs:
   CVE-2021-22890, CVE-2021-22876
   - This release bumps OpenSSL to 1.1.1k, fixing the following CVEs:
   CVE-2021-3450, CVE-2021-3449
   - This release bumps Ruby to 2.5.9, fixing the following CVEs:
   CVE-2020-25613, CVE-2021-28965
   - This release fixes a race condition that caused the agent to become
   disabled and no longer enforce desired state.
   - Previously, the puppet facts diff command, which compares Facter 3 and
   Facter 4 facts, did not run Facter 4 in a clean environment, causing
   undefined behavior for custom facts resolving. With this release, Puppet 4
   facts are read when running puppet facts in a new shell and custom facts
   resolve correctly.
   - Puppet Server now adds an extension for subject-alternative-name (SAN)
   when it signs incoming certificate signing requests (CSR).
   - The Jetty webserver now uses the local copy of the CRL from Puppet's
   SSL directory instead of the CA's copy.
   - Jetty has been updated to 9.4.40 to resolve security issues.
   - This release adds the cloud.provider fact for Azure identification on
   Linux and Windows platforms.
   - Previously, each time you executed require facter, the Facter and
   Puppet bin directories were added to PATH environment variable, even if
   they were already there. This is now fixed and require facter only adds
   Facter and Puppet bin directories to PATH if they are not there.

For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/6.22/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv2hamSKc0Xx%2BOccuLxWGHDwVBZgjyvgMdhQORtHmhuVKA%40mail.gmail.com.

[Puppet Users] Puppet Platform 7.6.1 is now available

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.6.1, is now available!

The release contains bug fixes, minor enhancements, and security fixes
including:

   - This release bumps Curl to 7.76.0, fixing the following CVEs:
   CVE-2021-22890, CVE-2021-22876
   - This release bumps Ruby to 2.7.3, fixing the following CVEs:
   CVE-2020-25613, CVE-2021-28966
   - Resolution of the following issues:
  - Race condition with agent_disabled_lockfile
  - Unable to install gems with the puppet_gem provider on Windows
  - Puppet cannot parse systemd instances when list-unit-files output
  has an additional column
  - This release includes minor dependency updates, including an update
  to Jetty 9.4.40 to resolve security issues.
  - Auto promoting dotted facts to structured facts is incompatible.
  - Facter breaks when querying custom facts.
  - Inconsistent handling of date types in custom facts.
   - Minor Enhancement:
  - The processors fact includes sockets and threads details.

For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv2QKPBTe-m2JwM%3DgHtHb2%2BGVi5C2mdATxPVUSviE_YA-w%40mail.gmail.com.

[Puppet Users] Bolt 3.7.0 is now available

[Puppet Product Updates]

VERSION 3.7.0

*in this release*

✨  *new features*

   - Do you need to invoke PuppetDB commands from a plan run? The new
   puppetdb_command plan function lets you do just that! Currently, the
   replace_facts command is the only command that is officially tested and
   supported, though other commands might work. For more information about
   using this plan function, see the documentation
   .
   *This plan function is experimental and subject to change.*
   - Bolt now defaults to showing all targets in the inventory when
running bolt
   inventory show or Get-BoltInventory without a targeting option.
   - The bolt group show and Get-BoltGroup commands now format human output
   similar to other show commands.

🔧  *bug fixes*

   - YAML plans with plan or task steps that include metaparameters (such
   as _catch_errors) no longer fail.
   - The bolt inventory show and Get-BoltInventory commands now display the
   correct source of the inventory. Previously, if the inventory source was
   the BOLT_INVENTORY environment variable, Bolt would display the path to
   the default inventory file.

VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pWGbP%3DkHmWQoqna33Z%2BY4zpYnmJTE9OeiHUczhMui%2BLjA%40mail.gmail.com.

[Puppet Users] Bolt 3.6.1 is now available

[Puppet Product Updates]

VERSION 3.6.1

*in this release*

🔧  *bug fixes*

   - Bolt now ensures that all messages from a command or script are
   printed to the console. Previously, some messages would not be printed to
   the console if they were read after a thread finished executing or if the
   command was executed with the run-as option.

VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pWt7sLmF11LVZFKqaE5aX-DQzjkYQ3mQQE57KjgFAOBtQ%40mail.gmail.com.

[Puppet Users] Bolt 3.6.0 is now available

[Puppet Product Updates]

VERSION 3.6.0

*in this release*

✨  *new features*

   - Analytics can now be disabled at the system, user, and project levels
   with the new analytics configuration option. To learn more about the
   data Bolt collects, or to see how to disable analytics, see the
   documentation .
   - Do you use Podman to run containers? Bolt has a new experimental
   podman transport that lets you connect to Podman containers and run actions
   on them. To learn more about this transport, see the documentation
   
.
   *This feature is experimental and is subject to change between minor
   versions.*
   - Bolt's human output when viewing inventory, plans, and tasks has been
   updated.

🔧  *bug fixes*

   - Bolt no longer stack traces when installing modules in a project
   without a bolt-project.yaml configuration file.


VIEW FULL RELEASE NOTES

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pUK9XxALeibOkTNmLD6DTg9M-OGaY6_nn%2BoFxpd_s6fMQ%40mail.gmail.com.

[Puppet Users] Bolt 3.5.0 is now available

[Puppet Product Updates]

VERSION 3.5.0

*in this release*

✨  *new features*

   - Plans that use the run_task_with() plan function can now be tested
   with BoltSpec. For more information about testing your plans with Bolt's
   built-in testing library, see testing plans
   .
   - You can now run Docker containers as a step in your plan using the new
   run_container() plan function. This function runs a Docker container
   with an optional command and returns its output. To learn more about using
   this new function, see the documentation
   
.
   *This feature is experimental and is subject to change between releases.*

   - The following bundled modules have been updated to their latest
   versions:
   - puppetlabs-aws_inventory
  
  - puppetlabs-gcloud_inventory
  

🔧  *bug fixes*

   - Bolt no longer warns about the plugin_hooks and version options being
   unknown options in an inventory file.

🚨  *deprecations*

   - Using dotted fact names in Bolt is now deprecated. For more
   information, see the related developer update
   

   .

VIEW FULL RELEASE NOTES


*in the works*

   - Performance improvements for Windows packages
   - Shipping the PuppetBolt PowerShell module to the PowerShell Gallery
   - Improvements to running scripts

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

March's highlighted feature is: *BoltSpec*!

*What is BoltSpec?*

BoltSpec is a library of helpers that ships with Bolt. It is intended to be
used with RSpec, a testing tool, to write unit tests for your plans.
Specifically, BoltSpec's helpers let you test the behavior of your plans
without the need to connect to targets.


*Why should I use BoltSpec?*

Because plans can include complex logic that automates different jobs, it's
important to test that the plan behaves as you expect. BoltSpec lets you
easily write tests for your plans so you can test their behavior in
development and catch any errors before your plans are used in production.
Also, because BoltSpec stubs out Bolt functions that connect to targets,
you don't need to worry about provisioning containers or VMs to run these
tests.


*How do I use BoltSpec?*

Using BoltSpec is as easy as installing and configuring rspec-puppet for
your module or project, and then adding a couple lines to your tests'
configuration file. If you already develop Puppet modules using the Puppet
Development Kit (PDK), then most of this is already done for you.

Going over all the details of using BoltSpec to test your plans is a little
much for an email. So if you're interested in testing your plans, why not
check out our new Testing Plans
 documentation?
VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pXhyYNJu9Faf7jWXqbr6fHnbZpk__DCr0vP2bhxLidW4g%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2021.0 is no longer GA

[Puppet Product Updates]

Hello

We know how critical the infrastructure is that you manage with Puppet. We
also know how important staying current with software releases is not only
for compliance reasons but to enable innovation. Based on early feedback,
we have made the decision to remove our PE 2021.0 release.

We are pulling this release because of an issue with one of the components,
which could cause errors with existing code bases. This issue could also
cause the upgrade to fail. We are actively working on the fixes, and these
fixes will be part of the next release (2021.1). Our decision is not due to
any potential or real security breaches; it is due only to an issue in the
product itself.

We’re targeting early May for a release. If you want to be notified when
new updates of PE are released, please email pe-us...@puppet.com and ask to
be added.

When 2021.1 is released, you can download it from the support portal.

We apologize for any inconvenience and please let us know if you have any
questions.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJiF0gpNpwcsvs%2BcAT8rksouuSHocCwd8SquSZp774Zh%3DMu7-g%40mail.gmail.com.

[Puppet Users] Bolt 3.4.0 is now available

[Puppet Product Updates]

VERSION 3.4.0

*in this release*

✨  *new features*

   - Bolt now merges output from stdout and stderr when running commands
   and scripts. When running Bolt with human-readable output, the output will
   now resemble what you would see when running the action directly on the
   target. Results from these actions, and JSON output, now include a new
   merged_output key in addition to the existing stdout and stderr keys.
   - You can now convert YAML plans by name instead of by file path when
   using the bolt plan convert command and Convert-BoltPlan cmdlet. For
   more information about converting YAML plans to Puppet language
plans, see the
   docs
   

   .
   - The prompt plan function has a new default option which you can use to
   set a default value for the prompt. If the user does not provide input, or
   stdin is not a tty, the function will return the default value. Check out
   the plan function reference
    to see
   how to use this function.
   - You can now prompt users to select an option from a menu of options
   with the prompt::menu plan function. To see how to use this function,
   check out the plan function reference
   .
   - The lxd transport has a new remote configuration option, which can be
   used to configure Bolt to connect to a remote LXD server. For a full list
   of configuration options available to this transport, see the transport
   reference
   .
   - Bolt now displays a welcome message to users running their first Bolt
   command if the command is bolt, bolt --help, or bolt help.
   - Bolt now ships with the latest versions of the
   puppetlabs-puppet_agent, puppetlabs-puppet_conf, and puppetlabs-reboot
   modules.

🔧  *bug fixes*

   - Bolt now properly validates that the env_vars option for the
   run_command and run_script commands is a hash, raising a helpful error
   message if it is not.
   - Hash and array values set under the env_vars option are now converted
   to JSON. Previously, these values were stringified and had Ruby-style
   syntax.
   - Bolt no longer errors when showing task information when the task has
   a parameter that does not define a type.
   - Bolt no longer errors when showing task information for a task that
   can run in no-operation mode.
   - Bolt now handles malformed _error values returned from tasks in the
   Orchestrator.

VIEW THE RELEASE NOTES


*in the works*

   - Performance improvements on Windows
   - Shipping the PuppetBolt module to the PowerShell Gallery
   - Improvements to running scripts
   - A plan function to run containers

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

March's highlighted feature is: *BoltSpec*!

*What is BoltSpec?*

BoltSpec is a library of helpers that ships with Bolt. It is intended to be
used with RSpec, a testing tool, to write unit tests for your plans.
Specifically, BoltSpec's helpers let you test the behavior of your plans
without the need to connect to targets.


*Why should I use BoltSpec?*

Because plans can include complex logic that automates different jobs, it's
important to test that the plan behaves as you expect. BoltSpec lets you
easily write tests for your plans so you can test their behavior in
development and catch any errors before your plans are used in production.
Also, because BoltSpec stubs out Bolt functions that connect to targets,
you don't need to worry about provisioning containers or VMs to run these
tests.


*How do I use BoltSpec?*

Using BoltSpec is as easy as installing and configuring rspec-puppet for
your module or project, and then adding a couple lines to your tests'
configuration file. If you already develop Puppet modules using the Puppet
Development Kit (PDK), then most of this is already done for you.

Going over all the details of using BoltSpec to test your plans is a little
much for an email. So if you're interested in testing your plans, why not
check out our new Testing Plans
 documentation?


VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send

[Puppet Users] The next release in the Puppet 7 series, Puppet 7.5.0, is now available!

[Puppet Product Updates]

The next release in the Puppet 7 series, Puppet 7.5.0, is now available!

The release contains bug fixes and minor improvements, including:

   - The puppet ssl show command -  which prints the full-text version of a
   host's certificate, including extensions
   - The ciphers setting - configures which TLS ciphersuites the agent
   supports
   - This release adds the GlobalSignRoot CA R3 certificate for rubygems.org

For the full list of changes, check out the release notes:
https://puppet.com/docs/puppet/latest/release_notes_osp.html

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJTbtgma2XWwGzND4DtAtLmywxfKRHCXMKOC7-kYjGfnHJs9Dg%40mail.gmail.com.

[Puppet Users] Bolt 3.3.0 is now available

[Puppet Product Updates]

VERSION 3.3.0

*in this release*

✨  *new features*

   - Do you need to connect to Linux containers? Bolt has a new lxd
   transport which can be used to connect to Linux containers and run actions
   on them. For more information on using this transport, see the experimental
   features
   

documentation.
   *This feature is experimental and might change between minor versions.*
   - Have a command or task that takes a long time to execute and want to
   see what's happening on the target? Bolt now supports streaming output from
   targets as actions are running. To learn how to stream output, check out
   the documentation
   

   .
   *This feature is experimental and might change between minor versions.*
   - YAML plan steps now support metaparameters as top-level step keys. For
   example, you can set a run-as user when running a command using the new
   run_as key. For a full list of YAML plan steps and supported keys,
see writing
   YAML plans
   .
   - Ever look at what plans are available in your project and wished that
   you could see each plan's description? You're in luck! Bolt now shows plan
   descriptions in bolt plan show and Get-BoltPlan output.
   - Running scripts from the command-line is easier than ever. Bolt now
   supports specifying a Puppet path (/

[Puppet Users] Bolt 3.1.0 is now available

[Puppet Product Updates]

VERSION 3.1.0

*in this release*

✨  *new features*

   - Bolt now automatically imports PowerShell modules that are included in
   a task's files list. PowerShell tasks no longer need to add separate
   Import-Module statements to include these extra files. For more
   information, see Writing tasks
   .
   - Bolt now ships with the powershell_task_helper module, which includes
   several helper functions for writing tasks in PowerShell. Learn more about
   using these helper functions in your tasks by checking out the
   documentation
    on
   the Forge.
   - The BoltSpec library now includes a config_data method that makes it
   easy to set Bolt configuration in tests for your plans. You can learn more
   about BoltSpec and overriding Bolt's configuration in tests by reading
   the documentation
   

   .

🔧  *bug fixes*

   - Bolt now supports using Puppet file syntax (
   puppet:///modules//) in apply blocks for files in a Bolt
   project. Previously, referring to these files using Puppet file syntax
   would result in an error.
   - The Result data type's to_data function now correctly serializes
   Sensitive task output.
   - Errors raised from running scripts in PowerShell on targets with an
   execution policy of Restricted or AllSigned now include clearer messages.
   - Bolt's inventory is now correctly exposed to the BoltSpec library.
   Previously, referencing targets in Bolt's inventory with BoltSpec would
   result in an 'Undefined method' error.

📚 *documentation*

   - We've officially added documentation for Bolt's built-in testing
   library: BoltSpec! This long-hidden (and incredibly useful) feature lets
   you easily write unit tests for your plans. Check out the documentation
   here .


VIEW FULL RELEASE NOTES


*in the works*

   - Look out for Windows Performance improvements coming soon.
   - We're working on a prototype for streaming output during remote
   execution.
   - Bolt will soon have a new transport that lets you connect to Linux
   containers.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
on what it is, why you might want to use it, and how it can be used in your
workflows.

March's highlighted feature is: *BoltSpec*!

*What is BoltSpec?*

BoltSpec is a library of helpers that ships with Bolt. It is intended to be
used with RSpec, a testing tool, to write unit tests for your plans.
Specifically, BoltSpec's helpers let you test the behavior of your plans
without the need to connect to targets.


*Why should I use BoltSpec?*

Because plans can include complex logic that automates different jobs, it's
important to test that the plan behaves as you expect. BoltSpec lets you
easily write tests for your plans so you can test their behavior in
development and catch any errors before your plans are used in production.
Also, because BoltSpec stubs out Bolt functions that connect to targets,
you don't need to worry about provisioning containers or VMs to run these
tests.


*How do I use BoltSpec?*

Using BoltSpec is as easy as installing and configuring rspec-puppet for
your module or project, and then adding a couple lines to your tests'
configuration file. If you already develop Puppet modules using the Puppet
Development Kit (PDK), then most of this is already done for you.

Going over all the details of using BoltSpec to test your plans is a little
much for an email. So if you're interested in testing your plans, why not
check out our new Testing Plans
 documentation?


VIEW THE DOCUMENTATION

[image: Tw]  [image: Yt]
 [image: In]


*Bolt Documentation *

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdD-pVrupp9_1SHoJaP0RaZG%2BVjz%3DrRd%2BBBeD6%2BunmV1NVpPQ%40mail.gmail.com.

[Puppet Users] Puppet Enterprise 2019.8.5 is now available!

[Puppet Product Updates]

The latest patch release for the current Long Term Support (LTS) version of
Puppet Enterprise, 2019.8.5, is now available!



This is a backward-compatible release that contains enhancements and bug
fixes, including:



   -

   A new patching plan that includes pre- and post-patching health checks,
   reducing manual steps for your patching process.
   -

   Performance improvements to PuppetDB. One customer saw a 750%
   improvement!

For the full list of changes, check out the release notes:
https://puppet.com/docs/pe/2019.8/release_notes_pe_index.html



Download PE 2019.8.5 here:
https://puppet.com/misc/pe-files/previous-releases/



As a current Puppet Enterprise user, you can update to this new version as
part of your annual subscription. When updating, you must update
infrastructure components first and then update agents. For detailed
instructions, see the documentation
.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJiF0gq3_BZBJtPfDyyB4PFu0m95YzjabLPgOGGO9mVrhWsRUw%40mail.gmail.com.