Issue #15904 has been updated by eric sorenson.
Status changed from Unreviewed to Rejected
Yes, that's the intent -- the path attribute of tidy specifies the starting
tree to begin the tidy. If it removed the directory itself, subsequent attempts
to `tidy` underneath it would fail because the parent is not there.
If you want to recursively remove the whole thing, use a simple file resource:
file { "/home/george":
ensure => absent,
recurse => true,
backup => false,
}
----------------------------------------
Bug #15904: Tidy does not remove directories
https://projects.puppetlabs.com/issues/15904#change-68953
Author: Dan White
Status: Rejected
Priority: Normal
Assignee:
Category: tidy
Target version:
Affected Puppet version: 2.6.16
Keywords: tidy
Branch:
In a node manifest:
<pre>
tidy { '/opt/home/users/george':
age => '0',
recurse => true,
rmdirs => true,
}
</pre>
/opt/home/users/george is a directory.
This resource definition will remove files, but it leaves directories.
Changing it to /opt/home/users/george/ makes no difference.
Using the **path** parameter instead of the default **path/namevar** makes no
differemce.
--
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://projects.puppetlabs.com/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.
