Issue #15668 has been updated by Andrew Parker. Status changed from Accepted to In Topic Branch Pending Review Branch set to https://github.com/puppetlabs/puppet/pull/968
https://github.com/puppetlabs/puppet/pull/968 ---------------------------------------- Bug #15668: Revert #12127 - Puppet should not pluginsync on 'puppet apply' https://projects.puppetlabs.com/issues/15668#change-67678 Author: eric sorenson Status: In Topic Branch Pending Review Priority: Normal Assignee: Andrew Parker Category: plug-ins Target version: 3.x Affected Puppet version: Keywords: pluginsync Branch: https://github.com/puppetlabs/puppet/pull/968 After some testing and clarifying the role of pluginsync in the ecosystem, it sure seems like #12127 was a bad idea. The root of the problem is that the pluginsync area is primarily a way for a master to deliver functionality to a puppet agent, which the agent needs in order to comply with the master. This could be to submit custom facts the master needs for compilation and/or to use types/providers the master specifies in the catalog that gets delivered. Pluginsync'ing from apply clobbers the local cache of these plugins with a totally disjoint set of plugins from the apply `modulepath` variable; apply should not be authoritative over the agent-to-master communication channel. Therefore the change in #12127 should be reverted; only `puppet agent` ought to initiate a pluginsync. -- 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.
