[[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]]Re: [[chef-dev]]CHEF-1621-"recursive" attributeon "directory" resource does not apply users and groups to entire path

[Thomas Bishop < >]

I'm wondering if that may cause confusion of when to use directory vs.
directory_tree.

'recurse_down_from' makes sense to me for defining the starting point.
 It does however lead me to believe that it would equate to running
chmod/chown -R from that point.  Perhaps adding another setting
(recurse_all_subcontent/children/entries?
include_subcontent/children/entries? other?) to denote that everything
in the tree will be set?

Examples:
directory "/data/realtime/fetched/radar" do
  recursive true
  recurse_down_from "/data/realtime"
  owner "ldm"
  owner "ldm"
  mode "777"
end

Would result in:
775 root:root /data
777 ldm:ldm /data/realtime
777 ldm:ldm /data/realtime/fetched
777 ldm:ldm /data/realtime/fetched/radar
The ownership/permissions of any dirs/files beneath
/data/realtime/fetched/radar/ would NOT be impacted


directory "/data/realtime/fetched/radar" do
  recursive true
  recurse_down_from "/data/realtime"
  recurse_all_subcontent true
  owner "ldm"
  owner "ldm"
  mode "777"
end

Would result in:
775 root:root /data
777 ldm:ldm /data/realtime
777 ldm:ldm /data/realtime/fetched
777 ldm:ldm /data/realtime/fetched/radar
The ownership/permissions of any dirs/files beneath
/data/realtime/fetched/radar/ would be 777 ldm:ldm

Thoughts?

-Tommy

On Tue, Oct 12, 2010 at 13:26, Seth Falcon 
<
 >
 wrote:
> On Tue, Oct 5, 2010 at 8:36 AM, Daniel DeLeo 
> <
 >
>  wrote:
>>> I definitely see the value in (1), but I think we can do better on
>>> (2). For example, what if you specify the top level directory to be
>>> managed, like:
>>>
>>>  directory("/data/realtime/fetched/radar") do
>>>    recursive true
>>>    recurse_upto "/data/realtime"
>>>    owner "not-root"
>>>    # other settings
>>>  end
>>>
>>> That way Chef knows which directories in the tree to manage, and when
>>> you change the owner or modes, Chef can update all of them.
>>>
>>> Thoughts?
>>
>> I think that's a good idea.  I tend to think of recursion going down,
>> so I might make the option 'recurse_downfrom'.
>>
>> One concern, it's a bit ambiguous whether 'realtime' should be owned
>> by root or not-root.  Maybe 'recurse_below' or something to that
>> effect?
>
> I wonder if a separate resource would allow us to avoid some of the
> confusion with terminology.  For example,
>
>  directory_tree "arbitrary label, not the path" do
>    from "/data/realtime"
>    to   "/data/realtime/a/deep/path/of/dirs/goes/here"
>    owner "not-root"
>    # other settings
>  end
>
> + seth
>