The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
puppet doc stopped accepting the environment flag between 0.25.5 and 2.6.1
|Affected Puppet version:||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This ticket may be automatically exported to the PUP project on JIRA using the button below:
Puppet doc (née puppetdoc) uses the three options having to do with manifest locations: manifest, manifestdir, and modulepath. Conveniently, these are the options you can set in environments. Puppetdoc was made environment-aware in issue #2783.
So in the 0.25 series, you could supply
--environment when invoking puppetdoc. Puppet doc appears to have stopped working entirely in 2.6.0, but it came back in 2.6.1 and hasn’t been able to accept the
--environment flag ever since; you’ve had to just specify the manifestdir/modulepath directly.
#1 Updated by Nick Fagerlund almost 3 years ago
Puppetdoc first started blowing up and not working at all in commit:df2d39248dd0bb2adc7b4f723722079cad2749ad, according to git bisect. But it’s not the same failure as we got in 2.6.0 proper — it’s a total explosion with the compiler terminus turning up missing.