Hi!
In jclouds-chef 1.6.0-rc.1 we've added a few properties to provide more control over how chef is installed when bootstrapping nodes.
This will help fixing most of the issues that are caused by the versions of rubygems or dependency gems without waiting for a bugfix release.
The following properties can now be used when creating the context (all are optional properties):
* ChefProperties.CHEF_VERSION - The version of the Chef gem to install. It accepts concrete versions, and also ranges like '>= 0.10.8', etc. If the proeprty is not set, the latest available version of the gem will be installed.
* ChefProperties.CHEF_GEM_SYSTEM_VERSION - The version of Rubygems to install (if not yet installed). By default will install version 1.8.10, to keep compatibility with previous jclouds-chef versions. However, this property can now be used to install the desired version of Rubygems.
* ChefProperties.CHEF_UPDATE_GEM_SYSTEM - Boolean property to force a "gem update --system" (or a "gem update --system <version>" if the previous property is set. By default is "false".
* ChefProperties.CHEF_UPDATE_GEMS - Boolean property to force a general update of the existing gems. By default is "false".
Hope this help to fix most of the issues that appear each time new gem versions are released.
Ignasi