Hi,
you could try something like
@@file { ...: tag => "my-exported-file" }
and on the receiver end:
File<<| tag == "my-exported-file" |>> {
path => "/my/different/path"
}
But even if that works, I'm not at all sure how sound it really is.
HTH,
Felix
On 03/20/2013 11:41 AM, Russell Parsloe wrote:
> I'm trying to use Puppet and PuppetDB to export a config file from one
> node, and collect it on another i.e.
>
> export */etc/app1/file1.cfg* from /node a/ and collect
> */etc/app2/file2.cfg* on /node b/.
>
> I need the contents of file1.cfg and file2.cfg to be the same, but the
> paths and file names themselves are different. I cannot centralise this
> file as it is generated at install time by node a.
>
> Is this even possible with Puppet? Although what I am trying to do
> removes the concept that Puppet should centrally manage and be
> authoritative for things, but if I can achieve this it would be very
> helpful.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
