Issue #6943 has been updated by Nick Fagerlund.
The answer is, "sort of." Luke doesn't think anyone's touched or used this code since he put it in, and is skeptical about it still working at all. I honestly don't understand it well enough to test it myself, and have never written a custom type or provider, which is the only way to use this. So that's why it's been languishing: no one is using it, and we haven't been able to determine whether they even should. ---------------------------------------- Feature #6943: Support client-side templates https://projects.puppetlabs.com/issues/6943 Author: James Turnbull Status: Needs More Information 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.
