that ensures that the new_resouce.updated_by_last_action state is properly captured when the dir contents change and when they don't.
so that converge and converge! are no longer a method in the provider and why_run, respectively. There is instead set_updated_status in provider. Everything is now converged in why_run's add_action, so neither of the converge methods should ever need to be called. Updated tests to reflect this. Removed all calls to converge, and replaced with set_updated_status only for tests that are looking at the update status of a provider, where the converge behavior has been mocked out.
is not longer updated_by_last_action on every run by only putting converge_by blocks in places where remote_dir would directly execute code.
* Use a single file to track order of operations between different steps in the tests * Use symbolic names when tracking order of operations so it's more human readable * Mark tests as unix_only, deploy doesn't support windows * Add tests that run a "migration"
The merge from 10-stable left this out on a limb because of the directory structure change.
default and override attributes are now split into components, so all the components need to be merged together to generate the serialized representation of a node. Unfortunately, this means that serializing a node is now lossy because the information about which component default and override attributes belong to is lost. In practice, this is not a major issue, since automatic, override, and default attributes are cleared by chef for each run.
Role and environment default/override attributes are now set on the node at run_list expansion time, using the appropriate new attribute components on Node::Attribute.
I reformatted Chef::Node::Attribute because the indentation was busted. The actual code change is that Attribute now has components for role_default, env_default, role_override, and env_override, and merges them according to the precedence given in the documentation. These new components are not yet wired in to Chef::Node, however.
removing daemonize option for windows
304 support was previously in #run_request, which is deprecated and going away. To support If-Modified-Since in the http_request resource, we need to add support for 304 to the api we're keeping.
It's redundant to have _rest in the method names, the class is named REST. ...that said, a ton of code uses the old method names, so add aliases for compatibility.
Conflicts: chef-expander/lib/chef/expander/version.rb chef-server-api/lib/chef-server-api/version.rb chef-server-webui/lib/chef-server-webui/version.rb chef-server/lib/chef-server/version.rb chef-solr/lib/chef/solr/version.rb chef/lib/chef/node/attribute.rb lib/chef/node.rb