Chef attributes

[leonardofl]

I think the Chef attributes model is pretty confusing, so maybe I'm talking rubbish, but I would like to propose the following: separate attributes we have to change in different environments in the node.json.

With environment, I mean local, staging and production.

By reading attributes/default.rb it's hard to know which attributes we have really to change before run the recipe on staging or production. Most of them can be left as they are.

So I believe it would be cleaner to place the "changing attributes" on the node.json.

Obs: in local environment, the node.json attributes are declared on the .kitchen.yml file.

So, here it goes the attributes I believe should go to node.json:

• environment
• db.root_password
• db.polignu.password
• db.poligen.password
• linux_user
• server_name

I'm still confused about the authorization attributes group and the nginx.real_ip_from attribute.

Since now we are using the 443 port on the .kitchen.yml, maybe we can forget the ssl_public_port attribute and just use the 443 value wherever it's needed.

What do you think Diego?