Re: [Puppet-dev] how to allow user specified property names in provider code

2012-05-05 Thread Luke Kanies
On May 4, 2012, at 2:19 PM, Philip Brown wrote: > > > On Friday, May 4, 2012 1:42:35 PM UTC-7, Chris Price wrote: > I'm not an expert on the topic, but my understanding is that you can't create > a type without well-defined property/parameter names. Or, to put it a > different way, there is cu

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

2012-05-05 Thread Luke Kanies
On May 3, 2012, at 1:25 PM, Trevor Vaughan wrote: > All, > > I've noticed an understandable correlation between catalog size and > config retrieval time. However, I'm a bit lost as to why it seems so > slow. > > For an example 1.5M catalog: > > 24 seconds compile time > Almost instantaneous tra

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Philip Brown
On Saturday, May 5, 2012 7:42:43 PM UTC-7, Luke Kanies wrote: > > > Sorry - I meant it needs to be in the definition of the relevant property, > which in this case is 'ensure' (but in exec is 'returns'). > > For those "following along at home", that apparently means that, rather than the nice

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Luke Kanies
On May 5, 2012, at 5:37 PM, Philip Brown wrote: On Saturday, May 5, 2012 3:56:13 PM UTC-7, Luke Kanies wrote: > > On May 5, 2012, at 3:52 PM, Philip Brown wrote: > > PS: oops, you didnt say which "exec.rb". provider/exec.rb does not have, > but type/exec.rb does. > > I tried moving it into my t

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Philip Brown
On Saturday, May 5, 2012 3:56:13 PM UTC-7, Luke Kanies wrote: > > On May 5, 2012, at 3:52 PM, Philip Brown wrote: > > PS: oops, you didnt say which "exec.rb". provider/exec.rb does not have, > but type/exec.rb does. > > I tried moving it into my type file, but it still does not seem to get > ca

[Puppet-dev] (puppetlabs/facter) Ticket/1.6.x/14332 ubuntu stubbing

2012-05-05 Thread wearetherobots
Please review pull request #195: Ticket/1.6.x/14332 ubuntu stubbing opened by (kbarber) Description: The tests for facter fail on Ubuntu because lsbdistid is not correctly stubbed. This patch fixes that small mistake by stubbing lsbdistid for all Linux tests, except where

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Luke Kanies
On May 5, 2012, at 3:52 PM, Philip Brown wrote: > > > On Saturday, May 5, 2012 3:35:10 PM UTC-7, Philip Brown wrote: > > > judging by all the xxx_to_s methods in the type directory though, there's > some interesting functionality here, that *really* needs to be documented :( > > wow. yes, it

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Philip Brown
On Saturday, May 5, 2012 3:35:10 PM UTC-7, Philip Brown wrote: > > > > judging by all the xxx_to_s methods in the type directory though, there's > some interesting functionality here, that *really* needs to be documented :( > wow. yes, it rely does. I ran across it in maillist.rb, as

[Puppet-dev] (puppetlabs/facter) Ticket/1.6.x/update redhat spec file

2012-05-05 Thread wearetherobots
On Sat May 05 22:33:39 UTC 2012 pull request #191 was closed. Ticket/1.6.x/update redhat spec file requested by (MosesMendoza) The pull request was merged by: kbarber -- You received this message because you are subscribed to the Google Groups "Puppet Developers" gro

Re: [Puppet-dev] Naming of new provider to be submitted

2012-05-05 Thread Philip Brown
On Saturday, May 5, 2012 1:40:36 PM UTC-7, Luke Kanies wrote: > > > First, is there a reason not to just maintain this as a module on the > forge? > > We're trying to keep the builtin types to the minimum that most people > will use, and are even doing things like moving the Nagios types to a

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Philip Brown
On Saturday, May 5, 2012 1:38:08 PM UTC-7, Luke Kanies wrote: > > > On Saturday, May 5, 2012 6:42:31 AM UTC-7, Philip Brown wrote: >> >> ... > > > Now the only major ugliness left, is that on successful trigger, the > --verbose output is: > notice: /Stage[main]//Sysprop[network/smtp:sendmail]/en

Re: [Puppet-dev] Naming of new provider to be submitted

2012-05-05 Thread Luke Kanies
On May 4, 2012, at 10:00 PM, Philip Brown wrote: > The good news is, I hope to have a new type/provider combo to submit to the > puppet source next week :) Seems like I'm making good progress. > > The bad news is, I now need to pick a name that's going to be good for the > long haul, before I s

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Luke Kanies
On May 5, 2012, at 7:48 AM, Philip Brown wrote: > > > On Saturday, May 5, 2012 6:42:31 AM UTC-7, Philip Brown wrote: > > > *Almost* done with this beastie! Now I just have to force it to return > "true" when things already look good! > ruby is wierd. sigh. I have > @resource[:value]cla

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Philip Brown
On Saturday, May 5, 2012 6:42:31 AM UTC-7, Philip Brown wrote: > > > > *Almost* done with this beastie! Now I just have to force it to return > "true" when things already look good! > ruby is wierd. sigh. I have > @resource[:value]claiming its value is "true" > and the output of a command

Re: [Puppet-dev] How to have "ensure" routines notify something changed

2012-05-05 Thread Philip Brown
On Friday, May 4, 2012 10:07:33 PM UTC-7, Dan Bode wrote: > > > .. > The main thing that Puppet really 'logs' is state transitions. (it also > logs command on debug, but the thing it is really designe to do is describe > system state transitions) > > - it a resource exists and is ensurable, > -