Objects matching the expression 'plugins'

• #534 puppetd should support syncing any kind of library file (code, library, plugins, syncing)
• #752 Extra or missing slashes break client pre-downloads (plugins)
• #891 create a unified plugins/ mount and collect modules' plugins/ there (modules, plugins)
• #1083 0.24.2.rc1 plugins mount broken (mount, plugins)
• #1129 Facts distributed via plugins in modules method are sync'd but not evaluated (facts, plugins, sync)
• AddingFacts Adding Custom Facts to Facter (custom, extend, extending, fact, facter, facts, module, plugins, recipe)
• PluginsInModules This page describes the deployment of custom facts and types via modules. It is supported in 0.24 onwards and modifies the pluginsync model supported in releases prior to 0.24. It is NOT supported in earlier releases of Puppet but may be present as a patch in some older Debian Puppet packages. Usage ----- Instead of using the existing pluginsync mechanism custom types and facts are now stored in modules. These custom types and facts are then gathered together and distributed via a file mount on your Puppet master called plugins. To enable module distribution you need to make changes on both the Puppet master and the clients. On the Puppet master, if you have an existing plugins section in your fileserver.conf, get rid of the path parameter (if you leave the path parameter in place, then the mount will behave like any other fileserver mount). Move your existing plugins from the directory specified in that path into the modules for which they are relevant. If you do not have any modules defined or the types and facts are not relevant to any particular module you can create a generic module to hold all custom facts and types. It is recommended that you name this module custom. Ruby libraries in your plugins directories behave like Ruby libraries in any other Ruby lib directory, and their paths need to match whatever Ruby would normally look for. For example, Ruby expects Puppet resource types to be in $libdir/puppet/type/$type.rb, so for modules you would put them here:: <MODULEPATH>/<module>/plugins/puppet/type Similarly, Facter facts belong in the facter subdirectory of the library directory:: <MODULEPATH>/<module>/plugins/facter So, if we are using our custom module and our modulepath is /etc/puppet/modules then types and facts would be stored in the following directories:: /etc/puppet/modules/custom/plugins/puppet/type /etc/puppet/modules/custom/plugins/facter For now, continue using factsync to distribute facts. Distributing them works fine with pluginsync, but Facter is not yet smart enough to load them. This will be fixed in the next Facter release. Turn on pluginsync and specify the pluginsource as the plugins mount on your Puppet master's fileserver. The plugindest option may also be needed for puppetd to correctly find any custom types. You must also currently specify factpath, so that the facts dropped by pluginsync are loaded by Puppet:: [main] pluginsync (custom, facts, modules, plugins, types)