Release of R10K 3

[Maggie Dreyer]

Hello!

TL;DR: We released R10K 3.0. This version contains some bug fixes, but now requires Ruby >= 2.3.

We released R10K 3 this morning. This release improves error messaging, streamlines configurability, and most notably drops support for versions of Ruby that are no longer supported. R10K 3 is only compatible with Ruby > 2.3. See the changelog for details.

If you already tried updating to 3.0.0 and ran into issues around version conflicts or CLI errors, please update to 3.0.1, which fixes these.

Note that we do not recommend making this update on Puppet 3 or 4, as the version of Ruby we ship with those releases is now unsupported.

Thanks!

The Server Team

[Maggie Dreyer]

Resending this to all of the original lists of this email, since I don't personally have the answer. Thoughts, Puppeteers?

On Wed, Sep 26, 2018 at 4:23 PM Jesse Reynolds <jesse.r...@puppet.com> wrote:

Very good, thanks Maggie. 

Random question but do you know if it's possible now to have r10k talk to forge.puppet.com (and forgeapi.puppetlabs.com) through a SSL re-encrypting proxy? I've tried and failed with the version of r10k in PE 2018.1.4 to have it take note of the organisation's CA certificate but have been unable to. Do you think it would work to place the org's CA cert into the rubygem's ssl_certs dir under /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/ssl_certs ? 

Thank you

Jesse

--

Jesse Reynolds

Professional Services Engineer

Adelaide, Australia

mobile: +61 414 669 790

jesse.r...@puppet.com

Puppet. The shortest path to better software.