Conflict with nginx cookbook about elasticsearch HOT 5 CLOSED

Hi, I nevery really wrapped my head around proper attribute setting in Chef, even after reading all available documentation and source code :) Node attributes should be over-rideable just by knife node edit, but the preferrable way is to use roles.

Could you try to change the attribute setting in the attributes/nginx.rb file to use the default[:nginx] notation, if it helps?

from elasticsearch.

Using default[:nginx] allows me to set a normal attribute using knife node edit. However, before this cookbook was pulled in as a dependency, I didn't need to set it at all. So it seems that the default[:nginx] in this cookbook overrides the default[:nginx] in the nginx cookbook. From the chef documentation, it appears to load cookbooks in alphabetical order. This cookbook is loaded first and it thus appears that the first 'default' attribute wins. It seems the simplest solution is to just copy from the nginx cookbook attributes/default.rb the platform specific block for setting the user. Then the two cookbooks would have the same defaults.

from elasticsearch.

So it seems that the default[:nginx] in this cookbook overrides the default[:nginx] in the nginx cookbook.
This cookbook is loaded first and it thus appears that the first 'default' attribute wins.

Yes, that is how attributes in cookbooks work, unfortunately.

It seems the simplest solution is to just copy from the nginx cookbook attributes/default.rb the platform specific block for setting the user.

Yes, sounds like a good idea, will update it.

from elasticsearch.

Should be fixed, verified to be running as "www-data" on Ubuntu, as "nginx" on CentOS.

from elasticsearch.

thanks! works for me.

from elasticsearch.