Issue #17228 has been updated by eric sorenson. Status changed from Unreviewed to Closed
Sorry, the pluginsync mechanism -must- have control over the contents of the plugin destination area. I'd suggest just putting the facts in a module's `lib/facter/` directory and using pluginsync to distribute them. Alternately you could deliver them using File resources to any other directory in your Ruby LOAD_PATH, just not the pluginsync target. ---------------------------------------- Bug #17228: pluginsync removes module specific facts https://projects.puppetlabs.com/issues/17228#change-76299 Author: Dima Nils Status: Closed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Hi, I observe the issue that by turning pluginsync on its no more possible to store module specific facts to /var/lib/puppet/lib/facter/. If some module has stored there its facts by File[], then a run with pluginsync would remove such facts from there. It is possible to avoid this? Is it possible to add custom facts by File to /var/lib/puppet/lib/facter/. ? Regards Dimitri -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
