daniel g 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. 

pluginsyncing happens before the configuration for a client is compiled. 
  Therefore it is fundamentally not possible to avoid distribution of 
code via pluginsync. If you really need more finegrained control, either 
use facter's confine mechanism, like Nicolas suggested, or distribute 
your code via file{}. Be aware though, that the latter will cause puppet 
runs which do not have the code/facts/custom types available and need to 
be guarded properly.


Regards, DavidS

--~--~---------~--~----~------------~-------~--~----~
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