This has been fixed upstream, and is targetted for 0.24.7, turns out it
wasn't a documentation bug afterall, but an actual bug.

Thanks for filing it,
micah

----- Forwarded message from [EMAIL PROTECTED] -----

From: [EMAIL PROTECTED]
Subject: [Puppet - Bug #1660] (Closed) tidy recurse section of documentation 
should list valid values
Date: Tue, 28 Oct 2008 04:50:48 +0000 (UTC)
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]

Issue #1660 has been updated by jamtur01.

Status changed from Ready for Checkin to Closed
Target version changed from unplanned to 0.24.7

Pushed in commit:"57e791b9e7da931e61dd8dfc0f68bd13cf2e6449" in branch 0.24.x
----------------------------------------
Bug #1660: tidy recurse section of documentation should list valid values
http://projects.reductivelabs.com/issues/show/1660

Author: micah
Status: Closed
Priority: Normal
Assigned to: jamtur01
Category: file
Target version: 0.24.7
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

----- End forwarded message -----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to