[Puppet-dev] (puppetlabs/puppet) Maint/2.7.x/fix pkg provider tests on 1.8.5

2012-03-07 Thread wearetherobots
On Wed Mar 07 22:29:20 UTC 2012 pull request #566 was closed. Maint/2.7.x/fix pkg provider tests on 1.8.5 requested by (daniel-pittman) The pull request was merged by: pcarlisle -- You received this message because you are subscribed to the Google Groups "Puppet Deve

[Puppet-dev] (puppetlabs/puppet-acceptance) (maint) adding answer for _auth_database_name

2012-03-07 Thread wearetherobots
On Wed Mar 07 19:16:33 UTC 2012 pull request #162 was closed. (maint) adding answer for _auth_database_name requested by (djm68) The pull request was merged by: justinstoller -- You received this message because you are subscribed to the Google Groups "Puppet Develop

[Puppet-dev] (puppetlabs/puppet-acceptance) (maint) adding answer for _auth_database_name

2012-03-07 Thread wearetherobots
Please review pull request #162: (maint) adding answer for _auth_database_name opened by (djm68) Description: q_puppet_enterpriseconsole_auth_database_name is a new entry for the PE installer. Opened: Wed Mar 07 19:15:26 UTC 2012 Based on: puppetlabs:m

[Puppet-dev] (puppetlabs/puppet) (#7986) Modify pkg provider to handle publisher

2012-03-07 Thread wearetherobots
On Wed Mar 07 19:08:43 UTC 2012 pull request #560 was closed. (#7986) Modify pkg provider to handle publisher requested by (stschulte) The pull request was merged by: daniel-pittman -- You received this message because you are subscribed to the Google Groups "Puppet

Re: [Puppet-dev] Re: Interest in jruby specific tickets for facter/puppet?

2012-03-07 Thread Raphael Valyi
On Wed, Mar 7, 2012 at 2:59 PM, Daniel Pittman wrote: > On Tue, Mar 6, 2012 at 20:51, Raphael Valyi wrote: > > > I should say I was trying to achieve the same - running on JRuby - not > > on Puppet but on Chef. Specially it breaks on the ShellOut part of > > Chef where Chef mimics bash calls unde

Re: [Puppet-dev] Re: Interest in jruby specific tickets for facter/puppet?

2012-03-07 Thread Daniel Pittman
On Tue, Mar 6, 2012 at 20:51, Raphael Valyi wrote: > I should say I was trying to achieve the same - running on JRuby - not > on Puppet but on Chef. Specially it breaks on the ShellOut part of > Chef where Chef mimics bash calls under different file descriptors in > forked process. More specifica

[Puppet-dev] (puppetlabs/puppet-acceptance) (maint) bump puppet version to 2.7.12

2012-03-07 Thread wearetherobots
On Wed Mar 07 17:27:50 UTC 2012 pull request #161 was closed. (maint) bump puppet version to 2.7.12 requested by (justinstoller) The pull request was merged by: mykhyggz -- You received this message because you are subscribed to the Google Groups "Puppet Developers"

[Puppet-dev] Re: Array type on custom provider

2012-03-07 Thread David C
Yea, I had done: images = resource[:images] images = images.to_a which is kind of similar. Thanks to you I know another trick now. Thank you very much. On 7 mar, 17:32, markus wrote: > On Wed, 2012-03-07 at 07:33 -0800, David C wrote: > > Hi! > > > I'm creating a provider for my own type. In th

[Puppet-dev] Re: Array type on custom provider

2012-03-07 Thread David C
Thank you very much, that solved the issue. On 7 mar, 17:27, Nan Liu wrote: > If you want all elements of the array you need to declare the property as: > > newproperty(:images, :array_matching => :all) do > ... > end > > Otherwise, puppet will provide each array value separately which is > why y

Re: [Puppet-dev] Array type on custom provider

2012-03-07 Thread markus
On Wed, 2012-03-07 at 07:33 -0800, David C wrote: > Hi! > > I'm creating a provider for my own type. In the manifest I declare one > of the parameters as an array. When the array has only one element > (one string) running "puppet apply --debug init.pp" throws the > following error: > --- > change

Re: [Puppet-dev] Re: Array type on custom provider

2012-03-07 Thread Nan Liu
If you want all elements of the array you need to declare the property as: newproperty(:images, :array_matching => :all) do ... end Otherwise, puppet will provide each array value separately which is why you are getting a string. If this isn't the issue, a paste of your type/provider on pastebin

[Puppet-dev] Re: Array type on custom provider

2012-03-07 Thread David C
I forgot to say: puppet version: 2.7.9 facter version: 1.6.4 ruby version: 1.8.7 I also forgot to say thanks. On 7 mar, 16:33, David C wrote: > Hi! > > I'm creating a provider for my own type. In the manifest I declare one > of the parameters as an array. When the array has only one element > (o

[Puppet-dev] Array type on custom provider

2012-03-07 Thread David C
Hi! I'm creating a provider for my own type. In the manifest I declare one of the parameters as an array. When the array has only one element (one string) running "puppet apply --debug init.pp" throws the following error: --- change from absent to running failed: Could not set 'running on ensure: