Issue #5012 has been updated by Stefan Schulte.
2) No this behaviour is not new I just misunderstood the term Affected version (because I thought like "still not fixed in 2.6.1" instead of "its a bug since Version X") and I guess you're right about the feature request. Is there a possibility to change a bug into a feature? 1) It just autorequires the parent directory (unless there is no parent directory) so it behaves exactly like the file autorequire (its basically a copy of the `autorequire(:file)` block). I guess that is sufficent because when you manage `/x` and `/x/y/z` you will most likely also manage `/x/y` and have the dependency chain `/x/y/z` requires `/x/y` requires `/x`. ---------------------------------------- Bug #5012: File should autorequire Mounts https://projects.puppetlabs.com/issues/5012 Author: Stefan Schulte Status: Needs more information Priority: Normal Assignee: Category: file Target version: Affected version: 2.6.1 Keywords: Branch: I want to control mounpoints and files with Puppet. This is a common example: file {'/foo': ensure => directory} mount {'/foo': ensure => mounted } file {'/foo/bar': ensure => file} Unfortunately `File[/foo/bar]` just autorequires `File[/foo]` so it can happen that puppet creates `/foo` and `/foo/bar` and then mount `/foo`, so `/foo/bar` disappears and consumes diskspace. Because I cannot think of an use case where a directory or file does NOT depend on the parent mount, I propose to add an autorequire statement in the file-type. -- 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.
