On Fri, Sep 24, 2010 at 12:34 PM, Nan Liu <[email protected]> wrote: > On Fri, Sep 24, 2010 at 11:20 AM, Nigel Kersten <[email protected]> wrote: >> eg the proposal is that if you don't specify the protocol, server >> address, modules prefix, module name, it is assumed you are referring >> to a file path relative to the 'files' subdirectory of the current >> module. >> >> If you wish to fully specify the source URI, you're free to do so. > > Since we can determine module_name in 2.6, I agree with this change. > But we should update template behavior so it's the same as file. > Currently for templates: > > content => template("foo.erb"), > > Puppet would look in $templatedir/foo.erb which is > /var/lib/puppet/template/foo.erb, rather than foo module templates > directory. > > If we make this change for files we should have both behave the same.
Well that's a function, which does behave differently anyway. I have a similar proposal for the file function to behave exactly like the template function. I'd be reasonably happy to reduce my proposal to require the modulename, but I still think it's redundant info in the majority of cases, but I guess the $module_name variable mitigates this somewhat. > > Thanks, > > Nan > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. > > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
