One benefit of ripieenar's non native one though is that it creates a file resource for the destination file, so if you try to create another file resource for that file you get a proper duplicate resource declaration error. Is there any way to implement that protection with a native resource like this?
-- Erik Dalén On Tuesday 18 December 2012 at 05:00, Richard Pijnenburg wrote: > Hi all, > > I got a native file concat library which i believe could be very useful. > Current implementations of file concat's work with temporary files and finds > and can cause issues. > > the library can be found at > https://github.com/electrical/puppet-lib-file_concat > > Im pretty sure it will need some work to make it clean and lean but its a > good beginning i think. > > Wonder what you all think of this. > > Cheers. > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-dev/-/SHMnxjGYBD4J. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
