Issue #15300 has been updated by eric sorenson. Category set to plug-ins Status changed from Unreviewed to Accepted Assignee changed from Nigel Kersten to eric sorenson Target version set to 3.x Keywords set to pluginsync
The namespacing/load order is problematic but the files being copied on top of one another would be fixed if we replicated the module path structure from the master onto the client instead of squashing everything into $plugindest regardless of source. ---------------------------------------- Bug #15300: Pluginsync collisions https://projects.puppetlabs.com/issues/15300#change-67459 Author: Ben Ford Status: Accepted Priority: Normal Assignee: eric sorenson Category: plug-ins Target version: 3.x Affected Puppet version: Keywords: pluginsync Branch: I had a problem come up in training last week involving synced facts that brought out a larger problem in pluginsync. So if I create a module 'one' and define a fact in it called 'myfact', then create a module 'two' and also define a fact there called 'myfact' they will collide. The fact in 'two' will win because it comes later in the directory globbing. But worse is that they will be continuously fighting. On an agent run you can see this fact being overwritten to 'one/myfact' and then 'two/myfact' every single time. This is horrible for usability because it's not clear which fact will be called, and it's a terrible waste of bandwidth, etc. -- 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.
