[Puppet Users] Announcement: Release of Bolt 0.25.0

2018-10-05 Thread Kate Lopresti
Hello Everyone! We kick off the month with the release of Bolt 0.25.0. Added in this release is a return value for the apply action and a handful of bug fixes. For more information, see: https://puppet.com/docs/bolt/0.x/bolt_release_notes.html To try this new version, follow the installation

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread Eirik Øverby
> I would expect this to get into 5.5.7 but can't promise yet. Brilliant - as long as it's not me being crazy. Thanks again. /Eirik -- 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

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread kris . bosland
On Friday, October 5, 2018 at 11:22:30 AM UTC-7, Eirik Øverby wrote: > > > I've resuscitated my JIRA account, so if you wish to attach me to the > ticket in some way, my username is 'ltning'. > > I presume 5.5.7 should have this one fixed then? :) > > /Eirik I have set you as the Reporter.

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread Eirik Øverby
> Hi X, > > Nick Lewis helped me reproduce this issue with the extra module path, I have > filed https://tickets.puppetlabs.com/browse/PUP-9211 for the issue. > > Thanks! Thanks a *lot*! I've resuscitated my JIRA account, so if you wish to attach me to the ticket in some way, my username is

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread kris . bosland
On Friday, October 5, 2018 at 10:55:52 AM UTC-7, Eirik Øverby wrote: > > > Hi Eirik, > > > > I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165 > from https://github.com/puppetlabs/puppet/releases): > > > > kris.bosland@kris:puppet % git checkout 60de165

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread Eirik Øverby
> Hi Eirik, > > I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165 from > https://github.com/puppetlabs/puppet/releases): > > kris.bosland@kris:puppet % git checkout 60de165 >

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread kris . bosland
On Friday, October 5, 2018 at 8:20:51 AM UTC-7, Eirik Øverby wrote: > > On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley > wrote: > >> Hi Jon, >> >> In Puppet 6 we're going to start requiring that the names of >> classes/defines match the name that's implied by their file

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread kris . bosland
On Friday, October 5, 2018 at 8:20:51 AM UTC-7, Eirik Øverby wrote: > > On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley > wrote: > >> Hi Jon, >> >> In Puppet 6 we're going to start requiring that the names of >> classes/defines match the name that's implied by their file

Re: REGRESSION - Re: [Puppet Users] Announcement: Release of Puppet Platform 6.0.1

2018-10-05 Thread Eric Sorenson
Thanks for reporting this duritong - I wanted to follow up to say that this was fixed in 6.0.2 (indeed this was the reason we shipped 6.0.2 after 1 day:) ) On Wednesday, October 3, 2018 at 1:30:22 AM UTC-7, Peter Meier wrote: > > Hi All, > > > We're happy to announce the release of Puppet

[Puppet Users] Set default param value based on another param

2018-10-05 Thread Jody Des Roches
I'd like to set default values for parameters that will be passed to epp templates. However, the default value is based on another parameter. I understand that variables are immutable but this is a parameter that shouldn't be touched unless it wasn't set. Here is an example construct with a

Re: [Puppet Users] Recent 5.5.x point releases are throwing some warnings for me

2018-10-05 Thread Eirik Øverby
On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley wrote: > Hi Jon, > > In Puppet 6 we're going to start requiring that the names of > classes/defines match the name that's implied by their file path[1]. We > added that deprecation warning in 5.5.6[2] as part of a push to get