> The best part about having the documentation embedded in the types and > providers is that it's expressed in a Turing-complete language, so we have > to actually LOAD THE CODE to extract it.
Side issue but related: This also affects building packages for users for the forge if we want least effort github integration for example - whereby our systems build up the metadata.json on behalf of a user. I believe Cloudsmith wrote a parser in Java for this stuff for Geppetto for this kind of thing, and speaking to Tim Sharpe he had some suggestions as well for parsing this outside of Puppet. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
