On Nov 4, 2008, at 2:24 AM, Brice Figureau wrote:
> My concern is that puppetdoc right now doesn't use puppet.conf at all,
> and I'd like to keep this behavior. I want to be able to generate docs
> for a pile of manifests, modules or not. If I tie puppetdoc rdoc
> generation to puppet.conf :modulepath, then the only rdoc puppetdoc
> will
> be able to generate will be the manifests hosted on the current
> puppetmaster for a given environment.
>
> We could go this way (that'd be way simpler to know where the
> manifests
> are, or where the modules are), but then it fixes the documentation
> puppetdoc can generate (ie it'd be impossible to put some modules in a
> path and run puppetdoc over it).
>
> Or I could change puppetdoc rdoc to take more arguments like
> "--modulepath /path/to/modules" along with the path where to find the
> "global" (or site) manifests. If --modulepath is not mentionned then
> we
> assume that analysed path contains only modules.
I'd do that. Just generate docs for what people specify.
I'd also probably have puppetdoc accept standard ARGV arguments, and
consider those to be normal manifests, which it could then produce
output for on stdout. E.g., you could do:
puppetdoc manifests/site.pp
and it would give you docs for just that file, or, as you say, you
could do:
puppetdoc --modulepath <...> --manifest <...>
Maybe the --manifest becomes redundant at that point, though.
--
Finn's Law:
Uncertainty is the final test of innovation.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
