On Thursday, April 24, 2014 2:45:21 AM UTC-5, William Leese wrote: > > Hi, > > The accepted standard for sharing code seems to be modules, which doesn't > seem a nice fit if you simply want to share a single custom Puppet function. > >
Why not? > Having an easy way to look for Puppet functions would likely greatly help > the development of such, providing a nice set of examples and avoiding > duplicate work. > > I don't follow. If you don't like modules for this purpose, then what would be the characteristics of your ideal solution? > Currently I simply create a module for each function and upload to the > forge. Whats your approach? One monolithic module? Would that be easily > findable on the Forge (tagging won't scale)? etc. etc. > Custom functions are valuable and widely used, but they are not a focal feature of Puppet. It is uncommon for people to provide or seek a single custom function in isolation. Instead, people usually are after a broader facility. Typically that consists of classes and/or resource types (native or defined), possibly with associated custom functions. In other words, a module. If you are writing custom functions so general that they are not associated with any particular system configuration regime, then it might be suitable to collect several into a library module. PuppetLabs's 'stdlib' module follows this route (though it does provide a resource type or two along with the many functions). John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6c33bb67-d29d-4a11-9450-c545b469f655%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
