Affects Version/s: 0.9.6
Fix Version/s: None
Component/s: Chef Client
Running Chef 0.9.6 on CentOS 5
I am trying to set up a specific hierarchy of directories which must have correct permissions and owners. I do this:
directory "/data/realtime/fetched/radar" do
After that, I expect /data, /data/realtime, /data/realtime/fetched, and /data/realtime/fetched/radar directories to all exist, have owner "ldm", group "ldm", and permissions of 777.
Instead, all the directories exist, but only /data/realtime/fetched/radar has the correct user, group, and permissions; all others are owned by root (which ran chef-client) with 755 (default) permissions.
The documentation for this attribute comes from
which is not perfectly clear. This "bug" may be a bug in the code, which is doing the wrong thing by not respecting the "recursive" directive; or it may be a "bug" in the documentation, resulting in users like me not knowing exactly what the "recursive" attribute does. If I am expecting too much of the "recursive" attribute, then it would be good to expand the documentation to explain that "recursive" creates directories recursively, but does not apply other attributes recursively.