On 01/11/10 16:28, jcbollinger wrote: [ snipped full proposal ] > > To sum up: > > Resolving the perceived consistency issue can be done without any > change to the File resource. It is sufficient to > > a) Fix the relative path problem for the file() function, and > b) add a string concatentation function, and > c) deprecate passing multiple arguments to template(), prefering > instead applying the new conatentation function to several single- > argument invocations of template(). > > This approach is 100% backwards-compatible, inasmuch as deprecation of > multiple arguments to template() does not imply removal of that > feature. Because the new features would all be in functions, they > would be available everywhere in manifests that functions can be > invoked, not just in File resources. Furthermore, the new mechanism > for concatenating template results would be both more expressive than > the old and, because of its reliance on a general-purpose function, > more broadly consistent than just with file() and File/source.
+1, this is I think the best, and more or less what I was thinking when I read the OP mail. One thing I'd really don't want to lose (and some of the previous proposition removed it) is the hability to use: content => "my content" Thanks, -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
