On Dec 20, 2009, at 4:09 PM, Julian Simpson <[email protected]> wrote:
> 2009/12/18 Al @ Lab42 <[email protected]>: > [snip] >> 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. >> > > +1. > > Happy to agree the above. I'd rather specify less and get some broad > agreement on what makes the minimal and official/community compliant > metadata, than try and pin down every detail. I'd assumed that the > metadata would be in Ruby code, but equally happy with JSON or YAML. > > Julian. > This is a topic that is sure to come up in more detail soon, as I'm ramping up work on the [yet to be named] "module forge" and related client tools. I'd love to see some examples of what the community thinks should be present in the metadata -- especially information beyond the authorship and dependency information. Perhaps a wiki page is a good place to start (focusing on the information to be supported -- not the format, which is an implementation detail). Cheers, Bruce -- Bruce Williams http://reductivelabs.com -- 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.
