After all the Regex magic that has just ensued on the Dev list, this
should be pretty easy :-) (magic, I say!).
Having a regex match on the File type would actually be useful in a
lot of cases. *But* it needs to be able to be sped up.
Something like forking to the native tools to do the match and perms
might work, but at least something that gets rid of the 'recursive
directory management nightmare' where you checksum and/or record
millions of files just because you wanted to only change the
permissions.
In any case, you could then do thing like:
foo/ -> 755
foo/*.conf -> 640
foo/*.user -> 644
But, I could see ordering becoming quite important in this case.
Extremely low priority even if people do decide that it is a good idea.
Trevor
On Tue, Jul 28, 2009 at 05:47, Peter Meier<peter.me...@immerda.ch> wrote:
>
> Hi
>
>> OK, maybe I didn't express it clearly enough. Puppet won't let me
>> specify one behaviour for /a and another for /a/**. As I said, there
>> are valid reasons for wanting that.
>
> I understood it that way and I also understand the reasons. My problem
> is to see a valid way to describe that within the (existing or future)
> puppet language, as well to fit it into the resource model, which
> puppet is committed to.
>
> so something like?
>
> file{
> '/a:
> mode => 0755;
> "/a/**":
> mode => 0600;
> }
>
> but I'm not sure whether this wildcard resource is a good idea.
>
> cheers pete
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
