On Mon, Feb 14, 2011 at 3:30 PM, John Warburton <jwarbur...@gmail.com> wrote:
> On 9 February 2011 21:57, John Warburton <jwarbur...@gmail.com> wrote:
>>
>> OK - I found the issue. Because 2.6.x gives us nice human readable(ish)
>> catalogs, I compiled mine and the 'random' hits were all for directories.
>> Re-reading the manifest, I see those directories in the error messages all
>> had "type => directory", like
>>
>> file { "/var/empty":
>> ensure => 'directory',
>> type => 'directory',
>> mode => 755,
>>
> I was wondering how the type in the file resource for directories got in
> there. Maybe too enthusiastic reading of the manual? It seems it may have
> been ralsh from when it was working.
>
> Now that https://projects.puppetlabs.com/issues/3165 is resolved, I used
> ralsh on a directory with 2.6.5rc2, and it generated the same bad code!
>
> I have raised https://projects.puppetlabs.com/issues/6314
Thanks John. I'll do some clarification around your ticket, as we have
a wider problem with all read-only attributes.
I'm wondering whether it would be useful for puppet resource to have
an optional flag that did display read-only attributes? Certainly by
default we shouldn't be displaying them.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
