Issue #7585 has been updated by Nigel Kersten.
Given the power of pluginsync, in that you can use it to deploy providers that override the ones shipped by the Puppet core or even override other Ruby libraries core code might use, do you think it's still correct to default to true? ---------------------------------------- Feature #7585: Make pluginsync true by default https://projects.puppetlabs.com/issues/7585 Author: Cristian Ciupitu Status: Needs Decision Priority: Low Assignee: Nigel Kersten Category: plug-ins Target version: Affected Puppet version: 2.6.8 Keywords: Branch: Please make **pluginsync** `true` by default. I wasted a couple of days trying to figure out why a MySQL module wasn't working because of this. I agree that I should have read more of the [documentation](http://docs.puppetlabs.com/guides/plugins_in_modules.html#enabling-pluginsync), but it wouldn't hurt to use more reasonable defaults and let power users disable it if necessarily. I'm using puppet-server-2.6.8-1.fc14.noarch and puppet-2.6.8-1.el5. -- 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.
