Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix #2366 - puppetdoc was parsing classes in the wrong order | Brice Figureau | 2009-07-10 | 1 | -1/+2 |
| | | | | | | | | | | | | It could happend that we were generating doc for subclasses before classes, in which case we were forgotting some parent class instance and recreating them. We ended up generating doc for some classes multiple times, from which some were missing documentation. The fix is to sort the parsed classes alphabetically, which auto- matically puts enclosing class before enclosed classes. Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com> | ||||
* | Removed extra whitespace from end of lines | Ian Taylor | 2009-06-06 | 3 | -19/+19 |
| | |||||
* | Fix #1815 - puppetdoc --all crash on resource override | Brice Figureau | 2008-12-10 | 1 | -1/+1 |
| | |||||
* | Manifest documentation generation | Brice Figureau | 2008-11-17 | 4 | -0/+2536 |
There is currently two type of documentation generation for manifests (module or modulepath): * RDoc HTML generation for modules and global manifests * console output for sole manifest Both version handles classes, defines, nodes, global variable assignements, and resources when --all is used. The usage is the following: For the rdoc variant: $ puppetdoc --mode rdoc --outputdir doc It uses the puppet.conf configuration file to get the modulepath and manifestdir settings. Those are overridable on the command line with --modulepath and --manifestdir. For the console output version: $ puppetdoc /path/to/manifests Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com> |