Bug #6606
All autorequire rules should be documented
| Status: | Closed | Start date: | 03/05/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Nick Fagerlund | % Done: | 0% | |
| Category: | documentation | |||
| Target version: | 2.6.7 | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
Description
There are eleven resource types that will autorequire other resources, and their autorequire behavior is rather crappily documented. I propose that we put this info directly in the @doc for each affected type, so it’ll show up at the right point in the types reference automatically.
When I say “I propose” that, what I actually mean is that I just did it. Patches incoming based on 2.6.next.
History
#1
Updated by Nick Fagerlund over 2 years ago
- Status changed from Accepted to Merged - Pending Release
Pushed to 2.6.next in merge commit:609ddcf.
#2
Updated by James Turnbull about 2 years ago
- Status changed from Merged - Pending Release to Closed
Released in 2.6.7
#3
Updated by James Turnbull about 2 years ago
- Target version set to 2.6.7