The provider is idempotent and will not attempt to install the gem if it is installed.Thanks Guys! for clarifying.Is there any way to make the gem installation conditional? Like `only_if` ? So that the chef-client doesn't install those gems in each run?On Thursday, March 8, 2012 at 8:23 PM, Bryan McLellan wrote:
On Thu, Mar 8, 2012 at 4:43 AM, Sachin Sagar Rai < " target="_blank"> > wrote:What is the difference between the following following 2 gem installationmethods?gem_package "mysql" doaction :installendThis is used to install a gem to your system, such as when you'reinstalling a Ruby application to run as a service.r = gem_package "right_aws" doversion node['aws']['right_aws_version']action :nothingendr.run_action(:install)require 'rubygems'Gem.clear_pathsThis is used to install a gem immediately so you can use the gem in aChef recipe. In Chef 0.10.10+ this will be replaced by:chef_gem "right_aws" doversion node['aws']['right_aws_version']endBryan
Archive powered by MHonArc 2.6.16.