I'd like to start some discussion around how to implement https://projects.puppetlabs.com/issues/9546 (Plugin sync support for external facts)
Since external facts can be any type of executable and additionally straight json and yaml, i'm not sure putting then under lib/ is the best place to make the pluginsync magic happen. I was thinking it might make sense to add an extfact/ directory to the module structure that gets synchronized to $vardir/extfact which is then added to facters directory loader during the puppet run. So that's how to get the plugin magic to happen, now about providing expected results for facter. If a user has external facts that are being synced with puppet, they are going to probably expect "facter --puppet" to show those facts. So that's an update to load_puppet in facter. There's also then the question of compatibility. External facts were not supported in facter until 1.7. Is there currently a compatibility relationship between puppet and facter, or would this be the first one? What's the best way to handle this? Hard code the pluginsync to provide a warning that external facts will not be available until they upgrade to facter 1.7+? John -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
