Issue #12371 has been updated by Daniel Pittman.
I am happy with that proposal. We need to be careful: * if the change is under a path we "own" like `puppet` or `facter`, we should warn. * we should support something like `puppet/util` that you can throw random junk into as a user. * we should not warn for `foo` or other top level namespaces we *don't* own. We should also keep in mind changes to this list over time: we always have a master version >= the agent version, but the reverse is not true. That means if we introduce a new "supported" path in 4.0, a 3.0 agent might warn even once the master was upgraded. ---------------------------------------- Bug #12371: pluginsync should warn when files are not in a special directory https://projects.puppetlabs.com/issues/12371#change-54898 Author: Patrick Carlisle Status: Needs Decision Priority: Normal Assignee: Randall Hansen Category: Target version: Affected Puppet version: Keywords: Branch: If you put files in a module in a directory that doesn't get autoloaded there should be some sort of warning. -- 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.
