Issue #1660 has been updated by luke.

Status changed from Needs more information to Ready for Checkin
Assigned to changed from luke to jamtur01

Yeah, all of the recursion code is directly inherited from 'file', so 'tidy' 
should just have a 'newvalue' call added with the appropriate values.

Done in the tickets/0.24.x/1660 branch in my repo.
----------------------------------------
Bug #1660: tidy recurse section of documentation should list valid values
http://projects.reductivelabs.com/issues/show/1660

Author: micah
Status: Ready for Checkin
Priority: Normal
Assigned to: jamtur01
Category: file
Target version: unplanned
Complexity: Trivial
Affected version: 0.24.4
Keywords: tidy, type reference, file, recurse


The documentation which describes the recurse option of 'tidy' doesn't show the 
valid values, it should be more like the recurse section of 'file' 
(http://reductivelabs.com/trac/puppet/wiki/TypeReference#file) which describes 
the valid values:

"Whether and how deeply to do recursive management. Valid values are true, 
false, inf. Values can also match (?-mix:^[0-9]+$)."

Tidy simply says:

"If target is a directory, recursively descend into the directory looking for 
files to tidy."

People tend to think that the tidy { recurse => ... } values can be the same as 
the file values, and then put 'inf' in as a value, which does not work for tidy 
(you need to use recurse => true instead).




----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" 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-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to