Issue #4916 has been updated by Daniel Pittman. Assignee deleted (Daniel Pittman)
---------------------------------------- Bug #4916: Plugins should not be able to override core functionality. https://projects.puppetlabs.com/issues/4916#change-92395 * Author: Nigel Kersten * Status: Rejected * Priority: Low * Assignee: * Category: plug-ins * Target version: 3.0.0 * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- If you take core functionality like a provider, say puppet/providers/package/apt.rb and copy it to a module libdir, and then have pluginsync on... then anyone consuming that modulepath, regardless of whether they consume this particular module, will have this plugin override the core functionality. I think this is a problem. It really doesn't seem like a good idea from a security point of view for plugins to be able to override an equivalent core library. I understand that some people find this useful for patching functionality with providers. This doesn't make it right. They should instead be inheriting from the desired provider and specifying the provider they want. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
