Sometimes we get a good node object but it lacks the attribute that we
specified to use to connect to the node, so we should skip that too

If we don't skip nil items then the if condition fails with No Method error.
ie if !config[:override_attribute] && nil[:cloud] &&
nil[:cloud][:public_hostname] is obviously nonsense

Set /etc/chef/validation.pem and /etc/chef/encrypted_data_bag_secret
only readable by root.

This also corrects the test that was commented out for some reason

platform_specific_path could really use some work to handle these kinds of
situations. That would mean a bunch of testing and refactoring elsewhere
though.

Rubygems is placing executables under /usr/local/bin
on Ubuntu 12.04.  When using the 'init' init_style,
the following services do not start.
  chef-solr, chef-expander, chef-server, and chef-server-webui

knife data bag from file -a ; loads all data bags and items
knife data bag from file users -a ; loads all data bag items for data bag users

Adds support for:
knife environment from file foo.json bar.json
knife environment from file -a

"Add" is the verb used in the knife command to add items to the
run_list and for consistency it is convient for this same verb to be
available in chef-shell and knife-exec scripts.

If the server does not provide the endpoint the client will
continue without resource reporting.

I have no idea why these tests failed with multiple calls on 1.8 but passed
on 1.9.

Fixed a bug where update_new_file_state method in certain children of the file provider was causing @new_resource.mode to be changed before the actual file was changed by access_controls.set_all. This resulted in access_controls.set_all setting the wrong state (it set it to the current mode, rather than the new mode).

Removed node as argument from run_failed method in parent classes, as the child classes were reimplementing it with a different sig.

Conflicts:
	chef/lib/chef/resource_reporter.rb
	chef/spec/unit/resource_reporter_spec.rb