Issue #86 has been updated by Roy Nielsen.

...

    and this is exactly where this resource becomes unpredictable if on one host
/foo/bar/a exists but on one one host only /foo/bar and your tree should create 
/foo/bar/a/b/c
    
so - how do you do this now?

    one one host puppet would manage (owner, etc.) folder a on the other not, 
where it might 

Yes, if one wanted/needed a specific set of ownership on a tree, or part of a 
tree, that could/should be managed separate from the "create".  This would 
mandate the use of a "before" or "require"...

    be different and for example not chmod 0755 which would break access to 
your 
leave for the daemon, which would make the puppet-run incomplete and not able 
to 
set everything correctly. Or: what if you have 2 trees: /foo/bar/a/b/c and 
/foo/bar/a/e/f in one tree the owner is set to root in the other it is set to 
mail. On a vanilla host /foo doesn't exist. So what is owner /foo? Maybe root 
maybe mail? depends on which host which tree resource would have been applied 
earlier.

see above.

    Furthermore in the second run: how would puppet know from which part of the 
tree it manages that resource and what should it do if somebody changes in the 
above example permission of b ? In the first run it would set them correctly 
and then somebody changes it and what would it do then in the second run?

I see this (#86) as a "create" issue - not an issue of maintaining tree 
permissions.  That should be done as a different resource, with this as a 
"before", or be "required".

I see the "create_dir" option (maybe of ensure => ?) to handle ensuring the 
directories are created. 

but... I'm rather newish to puppet and target managing clients not servers so I 
may not be seeing this through the same pair of glasses :)

Regards,
-Roy

----------------------------------------
Feature #86: Directory creation fails if parent directory does not exist
http://projects.puppetlabs.com/issues/86

Author: Redmine Admin
Status: Accepted
Priority: Normal
Assigned to: 
Category: file
Target version: unplanned
Patch: None
Affected version: 0.24.7
Keywords: feature
Branch: 


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://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.

Reply via email to