I would like to start a new thread dedicated to the Modules metadata discussion. At the Puppet Camp and on this list there has been discussion about this. I might have missed some bits, but afaik there's not yet a formal decision about that. So if anyone knows more, please update me.
It has been discussed the modules packaging format, the metadata format and of course the metadata info to provide. In order to sum up things, and avoid repeating things already written, I've found these references on the topic: 1- GIT COMMIT "Adding additional module metadata" by Luke http://github.com/lak/puppet/commit/3896288ff56b44ae6f5e1f0c2a8adc995a458f76 This is for sure the starting point: json format, some basic parameters: :source, :author, :version, :license, :puppetversion, :summary, :description, :project_page 2- THREAD: Module Standards discussion http://groups.google.com/group/puppet-users/browse_thread/thread/66b90ee0e3a229c2?hl=en Blake Barnett proposed a yaml example such as the following, the discussion then somehow has evolved on metadata format and modules packaging but the info outlined can be interesting: module_postfix.yml --- name: postfix version: 0.1 description: Yay.... postfix. provides: classes: postfix, postfix::ldap, postfix::gerbils definitions: - name: postfix_spamq description: Specifies blah de blah required_parameters: - name: ensure - parameter_options: present, absent default: present optional_parameters: native_types: postfixregex dependencies: native_types: parser_functions: modules: facter_plugins: 3- THREAD: Proposals for modules naming conventions http://groups.google.com/group/puppet-users/browse_thread/thread/eb0ee0dc312d1a4 Julian Simpson suggests: "Was there discussion on metadata for modules? I know Luke was experimenting with that. I'd love to see what OS(es) a module has been tested on, and what versions of Puppet." in another post he says: " I'd like to make a proposal around module metadata, so that you could declare things like: - this module depends on others - this module works for this list of $operatingsystems - this module uses this sysadmin strategy " +1 for info about testing results for different puppet versions and OS. --- Now, as a user, I think that it is important to know how to start to write metadata files: format and minimal required parameters. A final (?) decision is not to be rushed, but an indication of the format and on some basic parameters that won't be changed for sure is definitively welcomed. If from this thread comes out an "officially Puppet complant" example of a metadata file I'm an happy guy. My 2c Al -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
