Issue #86 has been updated by Alan Harder.
I'll try to answer based on my understanding of the IRC conversation yesterday,
but of course Robin can followup..
Peter Meier wrote:
> as I don't see the difference (except at one point root is the owner and @
> the other foo) I assume you forgot to remove the create_parents?
no, the create_parents can stay. here is the scenario:
file{"/some/very/deep/path": ensure => directory, owner => 'root',
create_parents => true }
You have this code in place for a while and it deploys to 10 hosts.. then you
change owner to 'foo' which gets updated on those 10 hosts and also deploys to
10 new hosts. With this strategy, any ancestor directories that need to be
created get perms/owner/group copied from the deepest existing parent, and the
leaf uses the resource settings. So say / has 755/root/root on all your
systems. Then the first 10 hosts get /some, /some/very and /some/very/deep
also created with 755/root/root. /some/very/deep/path originally gets created
with owner root, and the update only changes that dir to owner 'foo'. The next
10 systems will result in everything matching because /some, /some/very and
/some/very/deep again copy upwards from /, and only the leaf gets owner 'foo'.
Hope this helps.
> as far as I understood your proposal this would set permission even on
> /var/lib/cache and upwards, which definately wouldn't be what you'd like to
> do. So something like a stop point: /var/lib/cache/foo is imho definately
> necessary. So something like fragfutter's solution still seems to be
> necessary or you go with the current solution.
I think in this example /var/lib/cache/foo would be created with matching
perms/owner/group as /var/lib/cache, and "bar" would be created with mode 700.
----------------------------------------
Feature #86: Directory creation fails if parent directory does not exist
http://projects.reductivelabs.com/issues/86
Author: Redmine Admin
Status: Accepted
Priority: Normal
Assigned to:
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
-~----------~----~----~----~------~----~------~--~---
