On Fri, May 17, 2013 at 8:23 AM, Jeff Goldschrafe
<j...@holyhandgrenade.org> wrote:
>
> There are a few tickets floating around, like #7635, that deal with the
> inability to specialize templates in standard Puppet.
[...]
> Many people are already using this model
> manually with file sources, providing
> ["puppet:///modules/mymodule/myfile.${osfamily}",
> "puppet:///modules/mymodule/myfile"]. I'd love to see a less verbose
> alternative that a) does this automatically based on configuration data
> rather than code, and that b) works for templates.
I think the best solution would be to change the `template` function
to select the first entry, rather than concatenate, and allow users to
manually concatenate multiple `template` calls if they wanted it.
I understand the attraction of having an automatic, rather than
manual, model for searching. I don't think it is a realistic goal,
however, because of the wide variety of "search paths" that could be
desired. Explicitly spelling out what is searched seems like the best
balance of flexibility and extensibility to me.
--
Daniel Pittman
⎋ Puppet Labs Developer – http://puppetlabs.com
♲ Made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
