On Nov 3, 2010, at 3:47 PM, jcbollinger wrote:
>
>
> On Nov 3, 11:30 am, Patrick <kc7...@gmail.com> wrote:
>> This is what I wanted except reversed. I was assuming that find_first()
>> can't open or find files. It can only look at what it returned to it, so
>> the syntax would be:
>>
>> find_first( file('foo'), file('bar') )
>> or
>> find_first( template('foo'), template('bar') )
>> or even
>> find_first( file('foo'), template('bar') )
>>
>> I think this order gives you more flexibility. Also, you might be able to
>> put a generate() function in there to depending on implementation.
>
> That would work for me, too. The ability to find_first results from
> different kinds of content sources would be nice.
>
> For my suggestion I was assuming that template() and file() don't have
> a good way to signal errors. In particular, an empty result cannot be
> used for the purpose because it might be the valid and desired
> content. If there is a way to make that work then I'd like that
> alternative. If not, then I don't see why find_first() would not be
> able to find or open files when file() can do.
The biggest problem is that makes those context sensitive because find_first
wouldn't know if it should look in the "files" or the "template" folder. I
guess you could:
*) Name those functions differently depending on which it's looking for.
or
*) Have it always look in templates for .erb files and look in files or
everything else.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
