[Puppet-dev] Re: booleans in type properties.

2008-11-21 Thread Nigel Kersten
>> hmm. I'll clean up the code a bit and stick it up somewhere to make >> this conversation a bit more productive. > > Ok. http://github.com/nigelkersten/puppetplugins/tree/master git://github.com/nigelkersten/puppetplugins.git It's pretty skeletal at the moment as I haven't put the setting cod

[Puppet-dev] Re: booleans in type properties.

2008-11-21 Thread Luke Kanies
On Nov 21, 2008, at 11:35 AM, Nigel Kersten wrote: > > On Fri, Nov 21, 2008 at 9:19 AM, Luke Kanies <[EMAIL PROTECTED]> wrote: >> >> >> >> I agree there's something ridiculous going on here, but you shouldn't >> need to manually munge things. >> >> I'd start by adding debugging to your type to see

[Puppet-dev] Re: booleans in type properties.

2008-11-21 Thread Nigel Kersten
On Fri, Nov 21, 2008 at 9:19 AM, Luke Kanies <[EMAIL PROTECTED]> wrote: > > On Nov 21, 2008, at 10:52 AM, Nigel Kersten wrote: > >> >> I was trying to track down why a manifest that looks like this for >> my type: >> >> macauthorization {"system.device.dvd.setregion.initial": >> ensure => present

[Puppet-dev] Re: booleans in type properties.

2008-11-21 Thread Luke Kanies
On Nov 21, 2008, at 10:52 AM, Nigel Kersten wrote: > > I was trying to track down why a manifest that looks like this for > my type: > > macauthorization {"system.device.dvd.setregion.initial": > ensure => present, > shared => true, > } > > kept telling me: > > notice: //Macauthorization[syst