Issue #6943 has been updated by Nick Fagerlund.

Status changed from Needs More Information to Closed

Since it sounds like this is basically a completely unsupported feature, I'm 
closing the ticket for now. If there's a good reason for looking into this, 
especially if we end up finding a use for it in our own types and providers, we 
can re-open it later; until then, it's not worth worrying about. 
----------------------------------------
Feature #6943: Support client-side templates
https://projects.puppetlabs.com/issues/6943

Author: James Turnbull
Status: Closed
Priority: Normal
Assignee: Nigel Kersten
Category: 
Target version: 
Keywords: 
Branch: 
Affected URL: 


I've just pushed a commit to my repo in feature/resource_template that provides 
client-side templates.  The templates are evaluated with access to the 
specified resource's attributes.

They're mostly useful for building composite resources, maybe like so:
<pre>
... my resource code ...
  def generate
    Puppet::Type.type(:file).create :path => "/my/file",
      content => Puppet::Util::ResourceTemplate.new("/my/template", 
self).evaluate
  end
...
</pre>
This is a small patch, and will likely rarely be used (and probably never from 
within Puppet's core), but it's already in use at a client and will likely be 
used at other places that need to build composite resources or use an API to 
generate resources rather than using the language for specifying all of them.


-- 
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