[Puppet-dev] (puppetlabs/puppet-acceptance) (maint) support latest sles service pack

On Fri Apr 20 01:20:14 UTC 2012 pull request #196 was closed. (maint) support latest sles service pack requested by (justinstoller) The pull request was merged by: justinstoller -- You received this message because you are subscribed to the Google Groups "Puppet Deve

[Puppet-dev] (puppetlabs/puppet) Feature/2.7.14rc1/14101 improved dynamic scope warning message

On Thu Apr 19 23:51:26 UTC 2012 pull request #693 was closed. Feature/2.7.14rc1/14101 improved dynamic scope warning message requested by (zaphod42) -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this gr

[Puppet-dev] (puppetlabs/puppet) Feature/2.7.14rc1/14101 improved dynamic scope warning message

Please review pull request #694: Feature/2.7.14rc1/14101 improved dynamic scope warning message opened by (zaphod42) Description: The deprecation warning about different variable lookups didn't provide a lot of information that would aid in resolving the issue. It now pri

[Puppet-dev] (puppetlabs/puppet) (#13559) Promote new console output prototype to official.

Please review pull request #692: (#13559) Promote new console output prototype to official. opened by (daniel-pittman) Description: This makes the prototype new console the official, default, system-wide console in Puppet. This has some small, visible effects on error re

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 2:00 PM, Andrew Parker wrote: > A strict mode would help quite a bit. +1 Like etc etc ;-) -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- You received this message because you are subscribed to the Google Groups "Pu

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 11:26 AM, Andrew Parker wrote: > So the main, sane, use case for inheritance is to set resource defaults. That > is the same thing I've heard from others, so at least people seem to agree on > that :) Yep, that's all I used them for. >> Puppet could very desperately use a de

Re: [Puppet-dev] Three prototypes

On Apr 19, 2012, at 1:39 PM, Ken Barber wrote: >> An interactive puppet shell: >> https://github.com/lak/puppet/tree/prototype/master/puppet_shell >> >> The best tool I ever had for managing ldap directories was a simple, stupid >> tool I wrote called ldapsh: http://search.cpan.org/dist/ldapsh

[Puppet-dev] (puppetlabs/puppet) Bug/master/enc variables not overridden by node

On Thu Apr 19 21:45:22 UTC 2012 pull request #682 was closed. Bug/master/enc variables not overridden by node requested by (zaphod42) The pull request was merged by: pcarlisle -- You received this message because you are subscribed to the Google Groups "Puppet Develo

[Puppet-dev] (puppetlabs/puppet) (#14072) Allow faces to inline global setting docs

Please review pull request #690: (#14072) Allow faces to inline global setting docs opened by (jeffweiss) Description: Add display_global_option[s] to Face DSL. Add environment, and modulepath as display_global_options for existing module face. Add type for typed settings

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 1:49 PM, R.I.Pienaar wrote: > > > - Original Message - >> From: "Andrew Parker" >> To: puppet-dev@googlegroups.com >> Sent: Thursday, April 19, 2012 9:43:36 PM >> Subject: Re: [Puppet-dev] Changes to variable scoping in Telly >> >> >> On Apr 19, 2012, at 1:28 PM,

Re: [Puppet-dev] Changes to variable scoping in Telly

- Original Message - > From: "Andrew Parker" > To: puppet-dev@googlegroups.com > Sent: Thursday, April 19, 2012 9:43:36 PM > Subject: Re: [Puppet-dev] Changes to variable scoping in Telly > > > On Apr 19, 2012, at 1:28 PM, R.I.Pienaar wrote: > > > > > > > - Original Message

Re: [Puppet-dev] Three prototypes

> Interactive transactions:   > https://github.com/lak/puppet/tree/prototype/master/interactive_transactions > > This provides a simple prompt before changing any resource in a transaction, > with the idea being that you could give people like developers some control > over how Puppet ran on thei

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 1:28 PM, R.I.Pienaar wrote: > > > - Original Message - >> From: "Andrew Parker" >> To: puppet-dev@googlegroups.com >> Sent: Thursday, April 19, 2012 8:42:33 PM >> Subject: Re: [Puppet-dev] Changes to variable scoping in Telly >> >> I've got a branch of puppet that

Re: [Puppet-dev] Three prototypes

On Thu, Apr 19, 2012 at 1:39 PM, Ken Barber wrote: >> An interactive puppet shell: >> https://github.com/lak/puppet/tree/prototype/master/puppet_shell >> >> The best tool I ever had for managing ldap directories was a simple, stupid >> tool I wrote called ldapsh:  http://search.cpan.org/dist/lda

Re: [Puppet-dev] Three prototypes

> An interactive puppet shell: > https://github.com/lak/puppet/tree/prototype/master/puppet_shell > > The best tool I ever had for managing ldap directories was a simple, stupid > tool I wrote called ldapsh:  http://search.cpan.org/dist/ldapsh/ .  It wasn't > much of a shell (e.g., no autocomple

Re: [Puppet-dev] Changes to variable scoping in Telly

- Original Message - > From: "Andrew Parker" > To: puppet-dev@googlegroups.com > Sent: Thursday, April 19, 2012 8:42:33 PM > Subject: Re: [Puppet-dev] Changes to variable scoping in Telly > > I've got a branch of puppet that has dynamic scoping removed. > Considering the impact that thi

Re: [Puppet-dev] Changes to variable scoping in Telly

I've got a branch of puppet that has dynamic scoping removed. Considering the impact that this will have on things and my personal uncertainty about whether people will still be able to achieve everything they want to with puppet, I'd really like to get people to grab it and try it out. https:/

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 11:45 AM, R.I.Pienaar wrote: > > > - Original Message - >> From: "Andrew Parker" >> To: puppet-dev@googlegroups.com >> Sent: Thursday, April 19, 2012 7:16:40 PM >> Subject: Re: [Puppet-dev] Changes to variable scoping in Telly >> >> >> On Apr 19, 2012, at 9:38 AM,

Re: [Puppet-dev] Changes to variable scoping in Telly

- Original Message - > From: "Andrew Parker" > To: puppet-dev@googlegroups.com > Sent: Thursday, April 19, 2012 7:16:40 PM > Subject: Re: [Puppet-dev] Changes to variable scoping in Telly > > > On Apr 19, 2012, at 9:38 AM, R.I.Pienaar wrote: > > > - Original Message - > >> Fro

[Puppet-dev] (puppetlabs/puppet) (maint) Get provider specs working on windows

On Thu Apr 19 18:20:37 UTC 2012 pull request #689 was closed. (maint) Get provider specs working on windows requested by (jeffweiss) -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 10:58 AM, Jo Rhett wrote: > On Apr 19, 2012, at 9:24 AM, Andrew Parker wrote: >> What do you do with inheritance (classes or nodes) wrt variables? Avoid? >> Using a lot? Have a specific pattern that you follow? > > I have used inheritance for overriding an object -- since it

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 9:38 AM, R.I.Pienaar wrote: > - Original Message - >> From: "Andrew Parker" >> To: puppet-dev@googlegroups.com >> Sent: Thursday, April 19, 2012 5:30:29 PM >> Subject: Re: [Puppet-dev] Changes to variable scoping in Telly >> >> Absolutely. Debugging is always made fi

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 9:24 AM, Andrew Parker wrote: > What do you do with inheritance (classes or nodes) wrt variables? Avoid? > Using a lot? Have a specific pattern that you follow? I have used inheritance for overriding an object -- since it's the only thing that can accomplish that, but I found

[Puppet-dev] (puppetlabs/puppet) (maint) Get provider specs working on windows

Please review pull request #689: (maint) Get provider specs working on windows opened by (jeffweiss) Description: Define helper to provider an existing command for windows because "echo" is a shell interpreted command, not a proper executable. As a side note, a helper me

Re: [Puppet-dev] Changes to variable scoping in Telly

- Original Message - > From: "Andrew Parker" > To: puppet-dev@googlegroups.com > Sent: Thursday, April 19, 2012 5:30:29 PM > Subject: Re: [Puppet-dev] Changes to variable scoping in Telly > > > On Apr 19, 2012, at 1:21 AM, Ken Barber wrote: > > >> If I want a top-level variable, I'll

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 19, 2012, at 1:21 AM, Ken Barber wrote: >> If I want a top-level variable, I'll ask for one. If I want a node-level >> variable, I'd like to be able to ask for one (which I can't today afaik). I >> never want either of them unless I ask for them by name. >> >> Yes, I do. Or an option to e

Re: [Puppet-dev] Changes to variable scoping in Telly

On Apr 18, 2012, at 4:27 PM, Jo Rhett wrote: > On Apr 18, 2012, at 4:04 PM, Andrew Parker wrote: >>> On Apr 17, 2012, at 9:00 AM, Andrew Parker wrote: Has anyone seen something where a manifest used $::var in order to *not* get the value of $var that is overridden in a node? >>> >>> U

[Puppet-dev] (puppetlabs/puppet) Better warning about metaparameter redefinitions

Please review pull request #688: Better warning about metaparameter redefinitions opened by (ustuehler) Description: A definition such as the following, which redefines metaparameters: define contact_info($alias = undef) { ... } generates the following warning: wa

Re: [Puppet-dev] Changes to variable scoping in Telly

> If I want a top-level variable, I'll ask for one. If I want a node-level > variable, I'd like to be able to ask for one (which I can't today afaik). I > never want either of them unless I ask for them by name. > > Yes, I do. Or an option to enable that at least. I realize that many people > love

[Puppet-dev] (puppetlabs/puppet) (maint) Add provider confine :exists => nil spec

Please review pull request #687: (maint) Add provider confine :exists => nil spec opened by (jeffweiss) Description: Add a test for the provider confine exists when the value is nil. Related tests are failing when confine :exists => nil, but the confine :exists => nil ca

[Puppet-dev] (puppetlabs/puppet) Implement Array#drop for Ruby 1.8.5

On Thu Apr 19 07:11:16 UTC 2012 pull request #684 was closed. Implement Array#drop for Ruby 1.8.5 requested by (daniel-pittman) The pull request was merged by: jeffweiss -- You received this message because you are subscribed to the Google Groups "Puppet Developers"

Re: [Puppet-dev] (puppetlabs/puppet) (#14036) Handle upstart better

On 18.04.2012 23:15, wearetherob...@puppetlabs.com wrote: Please review pull request #681: (#14036) Handle upstart better opened by (jeffweiss) Description: Change the upstart provider to better handle the mix of some services that are upstart con