On Thursday, June 21, 2012 5:44:46 PM UTC-5, Nick Fagerlund wrote:
>
>
> inevitably, everyone always wants to try this: [...]
>
I don't! :-)
That's what I suspected you were getting at, so thanks for clarifying.
That node inheritance works like class inheritance has never bothered me in
the
On Wednesday, June 20, 2012 6:00:04 AM UTC-7, jcbollinger wrote:
>
>
> - oh, and don't ever use node inheritance.
>>
>
> Why not? I mean, is that just to avoid the known issues with dynamic
> scope, or does node inheritance introduce special problems in this
> context?
>
Well... because ine
On Tuesday, June 19, 2012 4:07:56 PM UTC-5, Nick Fagerlund wrote:
>
>
>
> On Tuesday, June 19, 2012 7:19:20 AM UTC-7, jcbollinger wrote:
>>
>>
>> Have I missed a change in plan for node variables, so that in Puppet 3
>> they remain accessible outside node declarations? Does that form of
>> dyn
Hi,
On 06/19/2012 10:24 PM, Jon Schewe wrote:
>
> Node scope is staying a thing, because it has to for the time being.
>
> - It's unfortunately anonymous, so there's no way to address it
> directly. You have to use the variable's short name to get there.
> - But you can most assu
On Tuesday, June 19, 2012 7:19:20 AM UTC-7, jcbollinger wrote:
>
>
> Have I missed a change in plan for node variables, so that in Puppet 3
> they remain accessible outside node declarations? Does that form of
> dynamic scoping live on?
>
>
Yeah, they're effectively a tiny island of dynamic sc
On Tue, Jun 19, 2012 at 3:41 PM, Nick Fagerlund <
nick.fagerl...@puppetlabs.com> wrote:
>
>
> On Tuesday, June 19, 2012 1:24:42 PM UTC-7, Jon Schewe wrote:
>>
>>
>> So what I'm currently doing is perfectly valid and should continue to
>> work with 2.8, I've just got a version that's giving me extr
On Tuesday, June 19, 2012 1:24:42 PM UTC-7, Jon Schewe wrote:
>
>
> So what I'm currently doing is perfectly valid and should continue to work
> with 2.8, I've just got a version that's giving me extra warnings. Correct?
>
>
Yup! ...sorry about that. Implementing those warnings correctly turned
On Tue, Jun 19, 2012 at 2:43 PM, Nick Fagerlund <
nick.fagerl...@puppetlabs.com> wrote:
>
>
> On Tuesday, June 19, 2012 11:02:55 AM UTC-7, Jon Schewe wrote:
>>
>>
>> Am I getting this right that instead of just leaving the functionality in
>> puppet I should now call out to another application to
On Tuesday, June 19, 2012 11:02:55 AM UTC-7, Jon Schewe wrote:
>
>
> Am I getting this right that instead of just leaving the functionality in
> puppet I should now call out to another application to have node-specific
> variables? This seems like a step in the wrong direction. It's really nice
On Tue, Jun 19, 2012 at 9:19 AM, jcbollinger wrote:
>
>
> On Tuesday, June 19, 2012 7:20:47 AM UTC-5, R.I. Pienaar wrote:
>
>> > Right now I'm referencing the variable as "<%= ldap_server %>" and
>> > puppet is complaining on startup about dynamic scoping and telling
>> > me this will break. So cl
On Tue, Jun 19, 2012 at 7:20 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
> > From: "Jon Schewe"
> > To: puppet-users@googlegroups.com
> > Sent: Tuesday, June 19, 2012 1:13:09 PM
> > Subject: Re: [Puppet Users] Re: Correct way to handle no
On Tuesday, June 19, 2012 7:20:47 AM UTC-5, R.I. Pienaar wrote:
> > Right now I'm referencing the variable as "<%= ldap_server %>" and
> > puppet is complaining on startup about dynamic scoping and telling
> > me this will break. So clearly this isn't the way to go otherwise I
> > wouldn't ha
- Original Message -
> From: "Jon Schewe"
> To: puppet-users@googlegroups.com
> Sent: Tuesday, June 19, 2012 1:13:09 PM
> Subject: Re: [Puppet Users] Re: Correct way to handle node-specific variable
> values in puppet 2.7
>
> Right now I'm referenc
Right now I'm referencing the variable as "<%= ldap_server %>" and puppet
is complaining on startup about dynamic scoping and telling me this will
break. So clearly this isn't the way to go otherwise I wouldn't have the
warning.
On Tue, Jun 19, 2012 at 7:06 AM, earthgecko wrote:
> Due to the doc
Due to the documentation not being specifically clear with regards to node
level variables and scoping. In 2.7 node variables they are local scope.
Therefore in your templates you call the ldap_server variable NOT
::ldap_server as it is not a top scope variable.
As I say, the document is not s
15 matches
Mail list logo
