Issue #86 has been updated by Roy Nielsen.


<opinion> 

Handling creating a directory tree should not be any different than "mkdir -p" 
when creating a directory tree.

Handling complex permissions should be a separate transaction/resource.

A stipulation can be made that when a directory tree is made, the "tree" only 
can have one set of permissions/owner/group - as specified in the resource.  
This would start with the directory that is missing, down to the leaf. - 

ie - if /opt/local was there, and the resource called for creation of 
/opt/local/lib/mylib/mysubdir the permissions/owner/group will start with the 
newly created directories, starting with "lib", and including "mylib" & 
"mysubdir".
    
Absent could just be a dangerous "rm -rf" at the leaf level specified. ie - 
using the above example if one wants to get rid of mylib/mysubdir, one would say

    path    => "/opt/local/lib/mylib",
ensure  => absent,
recurse => true,

As said above, any complex permissions/owner/group should be handled separately.

If people want the file resource to chown, chmod or chgrp with a "-R/r", that 
could also be done, but as a separate bug/feature.  (I would say something 
similar to absent... start at the point specified in "path" or "name")

</opinion>

exec's ok... but from the http://docs.puppetlabs.com/guides/types/exec.html 
page:

    There is a strong tendency to use exec to do whatever work Puppet can’t 
already do; while
this is obviously acceptable (and unavoidable) in the short term, it is highly 
recommended to
migrate work from exec to native Puppet types as quickly as possible. If you 
find that you are
doing a lot of work with exec, please at least notify us at Reductive Labs what 
you are doing,
and hopefully we can work with you to get a native resource type for the work 
you are doing.

Sounds like this is a feature that a lot of people want.

Just need to agree on what the feature does :)

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