Hi, we're currently transforming some ugly perl-based management scripts (which placed some config data on the client and then configured something with it) to puppet.
While it is definitely the best idea point to keep all that config data on the master ( using hiera, puppetdb, etc..) i am currently looking for an interim solution to incorporate some of this local config data into centrally managed manifests/classes. Hiera is always using central hiera data while running the puppet agent server-based and is not using any hiera files placed on the client by default, is there some way to get around that ( perhaps with some kind of a server->client precedence)? Hiera is installed on all clients. I know that I could achieve something like that with custom facts ( generating facts from those locally placed config files) but this is quite a lot and would bloat up facter :) Or a more elegant way to get around that ( apart from putting that data where it belongs: the puppetmaster :) )? thanks in advance,... -- 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/2b23c524-b6e1-4edf-8153-5110efb075d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
