Hi Axel, can you explain what you mean by opposite to those docs? There is a bug about this which FWIW is fixed in 3.0:
http://projects.puppetlabs.com/issues/13858? -=Eric On Tuesday, October 9, 2012 12:25:47 AM UTC-7, Axel B wrote: > > Hi Stefan, > > It is exactly as you said. It works now - with one of the modules' > type/provider symlinked into the *master's* global type/provider dirs. > > But - seriously? That would mean that I have to symlink/copy each of the > modules' facts to the global installation on the master, which is not only > ... really bad, but also actually exactly the opposite of the things stated > in http://is.gd/zMVyXK and http://is.gd/vZ9j8D ... . Is this a bug?? > > > Thanks a lot :) & greetings, > Axel. > > > > > > Am Montag, 8. Oktober 2012 18:45:46 UTC+2 schrieb Stefan Schulte: >> >> comes to mind is that the puppet *master* does not find the plugin. The >> >> Simply copy the files by hand or perform an agent run with pluginsync >> turned on on your master. Then restart your master. >> >> -Stefan >> >> -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/bzD2JNbp_koJ. 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-dev?hl=en.
