Issue #86 has been updated by phantez.
berge wrote:
> A usable workaround exists (courtesy of Volcane on #puppet):
>
> file{ ["/foo", "/foo/bar", "/foo/bar/baz"]: ensure => directory }
fragfutter wrote:
> a discussion on #puppet lead to the question "who owns the directories?". If
> puppet creates directories recursive, should it own them (setting permissions
> and stuff) or not. And should it also set rights on existing folders?
>
> To avoid implicit declaration one possible syntax would be:
>
> file { "/var/long/path/here": ensure => "directory", recursive =>
> "/var/long", owner => "foo", }
>
> this would update ownership (and create directories if they are missing) for
> /var/long/path and /var/long/path/here
The solution proposed by berge seems less generic but more explicit.
----------------------------------------
Feature #86: Directory creation fails if parent directory does not exist
http://projects.reductivelabs.com/issues/86
Author: admin
Status: Accepted
Priority: Normal
Assigned to: community
Category: file
Target version: unplanned
Complexity: Medium
Patch: None
Affected version: 0.24.7
Keywords: feature
I tried
file {"/usr/local/share/puppet/sopext/facter" :
ensure => directory,
recurse => true
}
but get erros that the parent diretories are not available.
--
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
-~----------~----~----~----~------~----~------~--~---
