On Sun, 2008-11-02 at 21:53 -0600, Luke Kanies wrote:
> On Oct 31, 2008, at 5:40 PM, Brice Figureau wrote:
> > Note:
> > * the current version only knows how to parse modules. It can't
> > parse sole
> > manifests or manifests that are not under a standard module hierarchy.
>
> This is a great start, though. Are you planning on adding these? Just
> supporting the standard site.pp in the 'manifest' setting would be
> sufficient.
Yes, I'd like to be able to parse everything. My concern is that right
now everything must be "logically" part of a module. I can invent a
special module for the manifests that don't belong to this module
(something along a "<site>" module for instance).
> >
> > * the current version fails if you have ruby plugins (facter or
> > other) in your
> > modules. This will be fixed soon I hope.
I think I have an idea for this, but I don't know if that will work. I
think it will be quite fragile, though as it will depend in the current
plugin API:
I think I'll parse the ruby code in a crude way, looking for strings
ala:
Facter.add("something") or newfunction(:blah, :type => :rvalue) and
backtrack to fetch the comments that are just before.
Then I'll associate those documentation objects to the module they
belong to.
> You should send a note to the user list, so the rest of the community
> has a chance to test.
I will do as soon as it will be a little bit more stable (ie right now
if you have ruby plugins it fails).
Thanks for your comments ;-)
--
Brice Figureau <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
