Bug #7907
puppet doc stopped accepting the environment flag between 0.25.5 and 2.6.1
| Status: | Accepted | Start date: | 06/13/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | regression | |||
Description
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.
History
#1
Updated by Nick Fagerlund about 2 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.
#2
Updated by Nick Fagerlund about 2 years ago
commit:644ad7e41880fe8c9e73a099e9d6644e19828f46 seems to be the first place the 2.6.0 “import loop detected” error shows up.
#3
Updated by Nick Fagerlund about 2 years ago
commit:760e418d254a8d2198d2c6eb466d783a5930ef47 is the first time puppet doc started actually working again post-2.6.0 (with environments broken).
#4
Updated by Nigel Kersten about 2 years ago
- Status changed from Needs Decision to Accepted
- Assignee deleted (
Nigel Kersten)
ugh.
#5
Updated by Nick Fagerlund about 2 years ago
- Keywords set to regression