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

[Daniel DeLeo < >]

Chad, I think you missed reply all on this one (I'm really terrible
about that myself) so I'm forwarding this back to the list -- Dan
DeLeo


---------- Forwarded message ----------
From: Chad Woolley 
<
 >
Date: Mon, Oct 4, 2010 at 7:50 PM
Subject: 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
To: Daniel DeLeo 
<
 >


On Mon, Oct 4, 2010 at 9:28 AM, Daniel DeLeo 
<
 >
 wrote:
> What worries me about setting the owner/permissions on the
> intermediate directories is that the final state of the system is
> dependent on the starting state, so if /data (for example) doesn't
> exist, you would end up with that directory owned by the user
> specified in the resource, but if it does exist and is owned (say) by
> root, it would stay that way.

OK, that's a very good reason :)

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

Thanks,
-- Chad