----- Original Message -----
> From: "Erik Dalén" <erik.gustav.da...@gmail.com>
> To: puppet-dev@googlegroups.com
> Sent: Tuesday, December 18, 2012 11:54:33 AM
> Subject: Re: [Puppet-dev] file concat library
>
> 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?
it also allows you to include non managed files into the final
result.
often you want users to edit some part of a file, lets say a motd
like:
Machine overview
- Machine notes
- Machine notes
Stupid security notice
you might want to give the machine owner the right to edit machine
notes while the systems team must be sure hte security notice is
always present, the concat module lets you do that.
concat::fragment{"motd notes": ensure => /etc/machine_notes}
this is something I used to use a lot and I've not seen it in the
native concat modules.
Apart from that at the very least the file writer in the provider
of this one must write to a temp file and move that rather than
directly overwrite the destination, LOTS can go wrong with that
approach
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
