you are right, at the current stage it doesn't scale well, a more realistic
scenario for me is that i have multiple version of the same fact in
different environments.

the solution that I can is to use factsync on the normal clients, and to use
pluginsync on my puppetmasters.
than in the puppetmaster manifest i distribute the facts, functions etc -
not perfect, but acceptable for now.

my 2 cents,
Ohad

On Tue, Jul 7, 2009 at 7:28 AM, daniel g <dan...@invisiblempire.com> wrote:

> It appears that pluginsync is syncing every custom fact in all modules in
> our puppetmasterd's modulepath, regardless of whether or not the modules are
> included for the node in the node list.
>
> Is there any way to ensure that only facts from modules that the client is
> including are synced, or is this the intended behavior and we should
> structure our custom facts/functions with this in mind?
>
> I've double checked the documentation and am not seeing anything
> specifically relevant.
>
> puppetmaster/puppetd @ 0.24.8, facter 1.5.5, ruby 1.8.5
>
> Thanks,
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to