> My idea wos now to take the Ressource "file" and put in the path-option the
> path to the share of the syslog-system, like so:
>
> file { "$hostname.conf":
> ensure => present,
> path => "//server/share/$hostname.conf",
> source => template("default_nxlog_debian/default.conf.erb")
> }
If I understand you correctly, then I think exported resources is what
you are looking for - assuming you want to put it into
/etc/something/$hostname.conf on the syslog server (for example) then
you could do something like...
(on the agents)
@@file { "/etc/something/${::hostname}.conf":
ensure => file,
content => template('default_nxlog_debian/default.conf.erb'),
tag => 'ngix_config_file',
}
This will cause the resource to be stored on the puppet master, rather
than applied to the node, you can then collect all the resources on
the syslog server by having something like this in the manifest....
File <<| tag == 'ngix_config_file' |>>
See: https://docs.puppetlabs.com/puppet/latest/reference/lang_exported.html
for more detailed docs.
Regards
Craig
--
Enviatics | Automation and configuration management
http://www.enviatics.com | @Enviatics
Puppet Training http://www.enviatics.com/training/
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CACxdKhGEw7pUiJgfShxU0fZeVqJ49%2B0nHEvyGaLdG%2BbHSARg7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
