Re: [Puppet-dev] Puppet 4: defined resource types and epp template

2016-02-04 Thread Martin Alfke
On 01 Feb 2016, at 19:15, Henrik Lindberg wrote: > > That is exactly what you should do. An external (file based epp) when called, > does not get to see variables in the scope from which it was called/used. > This design is deliberate. Think of the template

[Puppet-dev] Announce: puppet-agent 1.3.5 available

2016-02-04 Thread Morgan Rhodes
Puppet Agent 1.3.5 is now available! This is a security release that updates OpenSSL to 1.0.2f. See the release notes for the puppet agent package here: http://docs.puppetlabs.com/puppet/latest/reference/release_notes_agent.html To install or upgrade puppet-agent, follow the getting started

Re: [Puppet-dev] Re: ruby-1.9.3 in yum.puppetlabs.com

2016-02-04 Thread Michael Stahnke
On Fri, Jan 29, 2016 at 8:16 AM, Alex Harvey wrote: > Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is > so much in Puppet 4. However PE hasn't release Puppet 4 yet; my assessment > of the Puppet Forge is that not many modules out there are ready;

[Puppet-dev] Announce: Puppet 3.8.6 available

2016-02-04 Thread Morgan Rhodes
Puppet 3.8.6 is now available. This is a security release that updates OpenSSL to 1.0.2f for the Windows MSIs. There are no changes for non-Windows platforms. See the full release notes here: http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html For installation and upgrade

Re: [Puppet-dev] metaparam question

2016-02-04 Thread Kylo Ginsberg
On Wed, Feb 3, 2016 at 7:47 AM, R.I.Pienaar wrote: > hello, > > I would like to add a metaparameter - which I think is easy now via > Type.newmetaparam. > We haven't been thinking of metaparameters as a general purpose extension point. This came up once before that I know of,

Re: [Puppet-dev] Puppet 4: defined resource types and epp template

2016-02-04 Thread Martin Alfke
On 04 Feb 2016, at 14:30, Henrik Lindberg wrote: > On 2016-04-02 11:46, Martin Alfke wrote: >> >> On 01 Feb 2016, at 19:15, Henrik Lindberg >> wrote: >> >>> >>> That is exactly what you should do. An external (file based epp)

[Puppet-dev] Re: Puppet 4: defined resource types and epp template

2016-02-04 Thread Henrik Lindberg
On 2016-04-02 11:46, Martin Alfke wrote: On 01 Feb 2016, at 19:15, Henrik Lindberg wrote: That is exactly what you should do. An external (file based epp) when called, does not get to see variables in the scope from which it was called/used. This design is

[Puppet-dev] Re: Puppet 4: defined resource types and epp template

2016-02-04 Thread Henrik Lindberg
On 2016-02-02 21:15, John Bollinger wrote: On Monday, February 1, 2016 at 12:15:12 PM UTC-6, henrik lindberg wrote: Contrast this with the inline_epp, which you can think of as a lambda/code-block. Here the code block gets to see the variables in scope, since it is itself in that

Re: [Puppet-dev] metaparam question

2016-02-04 Thread Luke Kanies
> On Feb 4, 2016, at 3:35 PM, Kylo Ginsberg wrote: > >> On Wed, Feb 3, 2016 at 7:47 AM, R.I.Pienaar wrote: >> hello, >> >> I would like to add a metaparameter - which I think is easy now via >> Type.newmetaparam. > > We haven't been thinking of

[Puppet-dev] Re: Puppet 4: defined resource types and epp template

2016-02-04 Thread Henrik Lindberg
On 2016-04-02 14:40, Martin Alfke wrote: On 04 Feb 2016, at 14:30, Henrik Lindberg wrote: On 2016-04-02 11:46, Martin Alfke wrote: This especially feels bad, when we will have performance improvement for epp in the future. I have not seen tickets with