Issue #4920 has been updated by Nigel Kersten.

Content ends up in the catalog at catalog request time.
Source does not, and is served directly by the puppetmaster to the client at 
catalog application time.

Depending on your situation, there may be significant advantages in one 
approach over the other. You may wish to update files separately to manifests, 
or you may not wish to deliver file content at catalog request time.

It's not an implementation detail difference. There are quite different use 
cases, particularly if you manage mobile clients.

If you're claiming things "should" be a certain way, the onus is on you to 
explain what is unsatisfactory about the current implementation.
----------------------------------------
Feature #4920: Treat file sources as templates
http://projects.puppetlabs.com/issues/4920

Author: martin krafft
Status: Unreviewed
Priority: Normal
Assignee: 
Category: file
Target version: 
Affected version: 
Keywords: 
Branch: 


Under certain circumstances, file sources should be evaluated by ERB.
I imagine three possible syntax for that:

1. A parameter:
<pre>
file { "/tmp/file":
    source  => ["puppet:///$fqdn", "puppet:///somedefault"],
    erbeval => true
}
</pre>

2. A prefix:
<pre>
file { "/tmp/file":
    source  => ["puppet:///$fqdn", "erb:puppet:///somedefault"],
}
</pre>

3. Using the file extension:
<pre>
file { "/tmp/file":
    source  => ["puppet:///$fqdn", "puppet:///somedefault.erb"],
}
</pre>

In general, I would like to see the difference between files and templates
vanish. However, since ERB is dreadfully slow, that might not be desired.

Hence I would suggest a combination of (1.) and (2.) (stupid redmine syntax
parsing idiocy): erbeval defaults to false, in which case only the sources
prefixed with "erb:" are evaluated. If erbeval is true, all sources are
evaluated (and the prefix ignored). If wanted, a "noerb:" could also be
introduced.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" 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-bugs?hl=en.

Reply via email to