[chef] Re: Re: recursive directory lwrp ?

[Mike < >]

This is an oldie by goodie.

It's been discussed a fair amount of times, and the documentation reflects the current behavior:

https://docs.chef.io/resource_directory.html#recursive-directories

Namely, directing the user to specify all directories in the path they want the permissions scheme to apply in an Array.

-M

On Fri, Mar 13, 2015 at 5:26 PM, Steven Murawski < " target="_blank"> > wrote:

My guess is that since one or more of the folder in that path structure may already exist and be acl'd by other means.

The "workaround" is to specify the directories where you want the acl's defined.

It is more work, but forces you to be explicit about the settings you want controlled and it is work that is done once.

Other concerns with changing acls up the directory tree - do you only set the permissions on folders Chef creates? Or do you re-acl everthing in the path that is defined? 

There are a number of potential problems with setting acls on an undetermined number of ancestor directories as a general practice.

Steve

Steven Murawski

Community Software Development Engineer @ Chef

Microsoft MVP - PowerShell
http://stevenmurawski.com

On 3/13/2015 2:34:39 PM, Medya < " target="_blank"> > wrote:

as we all know, recursive true attribute of Directory resource, does not recursively create the directories with the owner that you mention in the resource,

I wonder what is the logical reason behind this design ?

and I also wonder if there is a recursive_directory resource I can use ? so it just creates all the directories recursively with the user and owner that I mention .