[[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

[Seth Falcon < >]

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