[Puppet Users] Announcement: Release of Bolt 0.21.3

[Kate Lopresti]

Hello Everyone!

Today we’re happy to announce the release of Bolt 0.21.3. In this release
you will find:

   - Support for TLS 1.2
   - Command completion for bash shell
   - Update to the Bolt analytics data collection

For more information on these new features and resolved issues, see:

https://puppet.com/docs/bolt/0.x/bolt_release_notes.html

To try this new version, follow the installation instructions for your
operating system at:

https://puppet.com/docs/bolt/0.x/bolt_installing.html


Thanks!
--
Kate Lopresti
Senior Technical Writer
kate.lopre...@puppet.com

-- 
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%2B%2Bkvaqfe_y91WuNWYkcRZwiVGwKXqLWeo%3D_YaCXkndn15%3DViA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

[Eric Sorenson]

On Jul 17, 2018, at 2:26 AM, Martin Alfke  wrote:
> 
>> On 17. Jul 2018, at 01:40, Eric Sorenson > > wrote:
>> 
>> So my question is - 
>> - do you current use/rely on 'gem install puppet' for your workflows? If so, 
>> what do you do with it? (does anybody use a 'gem install puppet' as their 
>> production "puppet agent" daemon?)
> 
> We install puppet as a gem in CI/CD unit testing.
> 

Hi Martin! Does this use depend on types and providers in puppet's lib/ 
directory? Or is it just having the core puppet code available?


>> - given the above, what would be the easiest/most intuitive way to get those 
>> extracted types into your puppet installation? some ideas we've kicked 
>> around are 
>>  * a puppet type 'meta module' that, akin to a rpm/deb metapackage, doesn't 
>> have content, just dependencies on the actual modules at particular pinned 
>> versions that match the agent package versions
>>  * a Puppetfile that you could point r10k at to get the modules installed
>>  * individual gems for each of the extracted modules with Gemfile 
>> dependencies (note: this is a Bad Idea™)
> 
> We need at least a note how we have to add the module with the separated 
> types/providers.

Yes absolutely

> 
>> 
>> WDYT?
>> --eric0
>> 
>> 
>>> On Jul 16, 2018, at 10:20 AM, Josh Cooper  wrote:
>>> 
>>> I wanted to share some significant developments as we progress towards a 
>>> Puppet Platform 6 release. I encourage you to try out nightly builds 
>>> available in the puppet6 repos:
>>> 
>>> http://nightlies.puppet.com/yum/puppet6-nightly/
>>> http://nightlies.puppet.com/apt/puppet6-nightly/
>>> http://nightlies.puppet.com/downloads/{mac,windows}/puppet6-nightly/
>>> 
>>> 1. Unvendoring Semantic Puppet
>>> 
>>> Previously, the puppet repo, puppet-agent and puppetserver 
>>> vendored/packaged different versions of the semantic_puppet gem. We've 
>>> untangled that mess so that in Platform 6:
>>> 
>>> * puppet has a runtime gem dependency on the semantic_puppet gem
>>> * puppet-agent bundles the semantic_puppet 1.0.2 gem
>>> * puppetserver no longer knows about puppet's transitive gem dependencies
>>> * we can bump the semantic_puppet version in puppet-agent in the future 
>>> without breaking puppetserver running on the same host. The same is true 
>>> for other puppet runtime gem dependencies like fast_gettext and multi_json.
>>> 
>>> See https://tickets.puppetlabs.com/browse/PA-1880 for more details.
>>> 
>>> 2. Puppet Platform 6 requires Ruby 2.3
>>> 
>>> Puppet Platform 6 requires Ruby 2.3 or up, so we can now use modern syntax 
>>> such as keyword arguments, dig, squiggly heredocs, etc. Puppet will error 
>>> when running on unsupported ruby versions such as 2.2, which went EOL on 
>>> March 31, 2018.
>>> 
>>> Since puppetserver runs puppet code in a JRuby interpreter and JRuby 1.7 
>>> conforms to the 1.9.3 Ruby language, we first had to move puppetserver from 
>>> JRuby 1.7 to 9K. In Platform 5, we made it possible to opt into using JRuby 
>>> 9K. In Platform 6, we will drop JRuby 1.7 and only support JRuby 9.1.x.x, 
>>> which conforms to Ruby 2.3.
>>> 
>>> To ensure puppet code does not break puppetserver/JRuby, we've started 
>>> running puppet PRs against JRuby 9K in TravisCI.
>>> 
>>> See https://tickets.puppetlabs.com/browse/PUP-6893 and 
>>> https://tickets.puppetlabs.com/browse/SERVER-2155 for more details.
>>> 
>>> 3. Intermediate CA improvements
>>> 
>>> Currently, customers can set up Puppet to use an intermediate CA by 
>>> manually generating and distributing certificates and keys, installing them 
>>> in the proper locations on disk, for both the master and agent. This is 
>>> time intensive, error prone, and even once these certs have been put in 
>>> place, full validation using CRL chains was not possible.
>>> 
>>> For Puppet 6, we we are making both tooling and functionality improvements 
>>> to this process. In this increment, we have implemented full validation 
>>> with chained certificates and CRLs, and we have changed the agent-side SSL 
>>> bootstrapping to automatically download these full chains from the master 
>>> and store and use them appropriately. It is now no longer necessary for 
>>> intermediate CA users to manually distribute SSL files to their agents. On 
>>> the server side, we are working to create a puppetserver CLI for setting up 
>>> and interacting with the CA. See 
>>> https://tickets.puppetlabs.com/browse/SERVER-2171.
>>> 
>>> 4. Server-stack containerization
>>> 
>>> We’ve been working primarily on the automation and tooling to improve 
>>> building and shipping updated containers for the Puppet Platform server 
>>> components (puppetserver, puppetdb, and r10k). The build tooling for these 
>>> containers has moved into the individual project repos, and we’re getting 
>>> very close to having containers that will auto-publish to dockerhub.
>>> 
>>> We also have a number of workflow improvements planned for running the 
>>> server stack in a 

[Puppet Users] Announce: Puppet Platform 5.5.4

[Garrett Guillotte]

Puppet Platform 5.5.4 is a bug-fix and feature release that includes
updates for Puppet 5.5.3, Facter 3.11.3, and pxp-agent 1.9.3. It also adds
Puppet agent packages for Fedora 28 and deprecates MCollective. For
details, see the puppet-agent release notes
.

PuppetDB 5.2.4 is a minor bug-fix release, and Puppet Server 5.3.4 adds
packages for Ubuntu 18.04 (Bionic Beaver). For details, see PuppetDB
 and Puppet Server
 release notes.

-- 
*Garrett Guillotte*
Technical Writer
garrett.guillo...@puppet.com

-- 
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/CAP7LywEZNqib4LCcZBsevnSMNyXSf_eOqG2G2drdB3VY%3DmwhpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Rspec failure with puppetdb_query (from termini package, not Dalen mod)

[Martin Alfke]

When using rspec-puopet we mock the puppetdb_query function.
Example can be found here: 
https://github.com/rodjek/rspec-puppet/issues/102#issuecomment-35568335

hth,
Martin


> On 17. Jul 2018, at 17:54, Russell Anderson  wrote:
> 
> Hopefully someone here can point me at the right solution.  I'd like to 
> include this puppetdb_query command in our suite of rspec tests, but can't 
> seem to get the right package requirements.  Please note, this isn't using 
> the Dalen mod, but rather the puppetdb api.
> 
> Code in question, functional on a test system:
> 
> 75: $_nodes = puppetdb_query("nodes[certname] {certname in 
> inventory[certname] {resources {type = 'Service' and title = 'alfresco'} } 
> and deactivated is null and expired is null}")
> 76: warning($_nodes)
> 
> On the test system, this produces a list of nodes as expected.  However, I 
> can't find the right combination of gems or ubuntu packages to get rspec to 
> pass.  I've tried adding a few gems by hand, so the list below is longer than 
> usual:
> 
> $ gem list --local | grep puppet
> md-puppetdb-terminus (2.0.0.3)
> ml-puppetdb-terminus (3.2.1.1)
> puppet (5.5.0)
> puppet-lint (2.3.6)
> puppet-strings (2.1.0)
> puppet-syntax (2.4.1)
> puppetdb-ruby (1.1.1)
> puppetdb-terminus (1.0)
> puppetdb_query (0.1.2)
> puppetlabs_spec_helper (2.9.1)
> quixoten-puppetdb-terminus (4.3.0)
> rspec-puppet (2.6.14)
> ruby-puppetdb (3.0.1)
> semantic_puppet (1.0.2)
> 
> error during compilation: Evaluation Error: Unknown function: 
> 'puppetdb_query'. (file: blah/blah/blah.pp, line: 75, column: 13)
> 
> -- 
> 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/3f545c61-fb83-4d36-a236-0f145780ba7b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/E8836061-3BA4-4AC2-908A-329ED382717B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Rspec failure with puppetdb_query (from termini package, not Dalen mod)

[Russell Anderson]

Hopefully someone here can point me at the right solution.  I'd like to 
include this puppetdb_query command in our suite of rspec tests, but can't 
seem to get the right package requirements.  Please note, this isn't using 
the Dalen mod, but rather the puppetdb api.

Code in question, functional on a test system:

75: $_nodes = puppetdb_query("nodes[certname] {certname in 
inventory[certname] {resources {type = 'Service' and title = 'alfresco'} } 
and deactivated is null and expired is null}")
76: warning($_nodes)

On the test system, this produces a list of nodes as expected.  However, I 
can't find the right combination of gems or ubuntu packages to get rspec to 
pass.  I've tried adding a few gems by hand, so the list below is longer 
than usual:

$ gem list --local | grep puppet
md-puppetdb-terminus (2.0.0.3)
ml-puppetdb-terminus (3.2.1.1)
puppet (5.5.0)
puppet-lint (2.3.6)
puppet-strings (2.1.0)
puppet-syntax (2.4.1)
puppetdb-ruby (1.1.1)
puppetdb-terminus (1.0)
puppetdb_query (0.1.2)
puppetlabs_spec_helper (2.9.1)
quixoten-puppetdb-terminus (4.3.0)
rspec-puppet (2.6.14)
ruby-puppetdb (3.0.1)
semantic_puppet (1.0.2)

error during compilation: Evaluation Error: Unknown function: 
'puppetdb_query'. (file: blah/blah/blah.pp, line: 75, column: 13)

-- 
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/3f545c61-fb83-4d36-a236-0f145780ba7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

[Martin Alfke]

> On 17. Jul 2018, at 01:40, Eric Sorenson  wrote:
> 
> Another effort that's underway but not yet complete is the extraction of 
> non-core types/providers into modules. This addresses some long-standing 
> requests to, for example, be able to change the nagios types and OS-specific 
> resources without needing to get a full agent release out. The extracted 
> types will be available in a modulepath structure in the puppet agent 
> package, so (with a few targeted exceptions) there won't be any user-visible 
> changes to what's available when you get the package, but an implication that 
> hasn't really come up is around using Puppet in rubygem format. The extracted 
> types are available on github and on the forge as separate modules, so if you 
> currently use some of these extracted types, you'd need a way to get them 
> installed locally.
> 
> So my question is - 
> - do you current use/rely on 'gem install puppet' for your workflows? If so, 
> what do you do with it? (does anybody use a 'gem install puppet' as their 
> production "puppet agent" daemon?)

We install puppet as a gem in CI/CD unit testing.

> - given the above, what would be the easiest/most intuitive way to get those 
> extracted types into your puppet installation? some ideas we've kicked around 
> are 
>   * a puppet type 'meta module' that, akin to a rpm/deb metapackage, doesn't 
> have content, just dependencies on the actual modules at particular pinned 
> versions that match the agent package versions
>   * a Puppetfile that you could point r10k at to get the modules installed
>   * individual gems for each of the extracted modules with Gemfile 
> dependencies (note: this is a Bad Idea™)

We need at least a note how we have to add the module with the separated 
types/providers.

> 
> WDYT?
> --eric0
> 
> 
>> On Jul 16, 2018, at 10:20 AM, Josh Cooper  wrote:
>> 
>> I wanted to share some significant developments as we progress towards a 
>> Puppet Platform 6 release. I encourage you to try out nightly builds 
>> available in the puppet6 repos:
>> 
>> http://nightlies.puppet.com/yum/puppet6-nightly/
>> http://nightlies.puppet.com/apt/puppet6-nightly/
>> http://nightlies.puppet.com/downloads/{mac,windows}/puppet6-nightly/
>> 
>> 1. Unvendoring Semantic Puppet
>> 
>> Previously, the puppet repo, puppet-agent and puppetserver vendored/packaged 
>> different versions of the semantic_puppet gem. We've untangled that mess so 
>> that in Platform 6:
>> 
>> * puppet has a runtime gem dependency on the semantic_puppet gem
>> * puppet-agent bundles the semantic_puppet 1.0.2 gem
>> * puppetserver no longer knows about puppet's transitive gem dependencies
>> * we can bump the semantic_puppet version in puppet-agent in the future 
>> without breaking puppetserver running on the same host. The same is true for 
>> other puppet runtime gem dependencies like fast_gettext and multi_json.
>> 
>> See https://tickets.puppetlabs.com/browse/PA-1880 for more details.
>> 
>> 2. Puppet Platform 6 requires Ruby 2.3
>> 
>> Puppet Platform 6 requires Ruby 2.3 or up, so we can now use modern syntax 
>> such as keyword arguments, dig, squiggly heredocs, etc. Puppet will error 
>> when running on unsupported ruby versions such as 2.2, which went EOL on 
>> March 31, 2018.
>> 
>> Since puppetserver runs puppet code in a JRuby interpreter and JRuby 1.7 
>> conforms to the 1.9.3 Ruby language, we first had to move puppetserver from 
>> JRuby 1.7 to 9K. In Platform 5, we made it possible to opt into using JRuby 
>> 9K. In Platform 6, we will drop JRuby 1.7 and only support JRuby 9.1.x.x, 
>> which conforms to Ruby 2.3.
>> 
>> To ensure puppet code does not break puppetserver/JRuby, we've started 
>> running puppet PRs against JRuby 9K in TravisCI.
>> 
>> See https://tickets.puppetlabs.com/browse/PUP-6893 and 
>> https://tickets.puppetlabs.com/browse/SERVER-2155 for more details.
>> 
>> 3. Intermediate CA improvements
>> 
>> Currently, customers can set up Puppet to use an intermediate CA by manually 
>> generating and distributing certificates and keys, installing them in the 
>> proper locations on disk, for both the master and agent. This is time 
>> intensive, error prone, and even once these certs have been put in place, 
>> full validation using CRL chains was not possible.
>> 
>> For Puppet 6, we we are making both tooling and functionality improvements 
>> to this process. In this increment, we have implemented full validation with 
>> chained certificates and CRLs, and we have changed the agent-side SSL 
>> bootstrapping to automatically download these full chains from the master 
>> and store and use them appropriately. It is now no longer necessary for 
>> intermediate CA users to manually distribute SSL files to their agents. On 
>> the server side, we are working to create a puppetserver CLI for setting up 
>> and interacting with the CA. See 
>> https://tickets.puppetlabs.com/browse/SERVER-2171.
>> 
>> 4. Server-stack containerization
>> 
>> We’ve