[chef-dev] Re: Re: Re: Installing Gems for a LWRP

[Ryan Hass < >]

I tried this for my LWRP, but the issue I have is the first execution results in an error being thrown due to the gem not being installed until after the node is converged. It seems like I may have to create a cookbook with the sole purpose of installing the required gem, and force the openssl cookbook to have a dependency on said cookbook; but doing so is pretty ugly.

-Ryan H.

On 05/02/2013 02:19 AM, Julian Dunn wrote:

" type="cite">

Ditto what he said, but check out what we do in the AWS cookbook.

https://github.com/opscode-cookbooks/aws/blob/master/libraries/ec2.rb#L44

Granted this is a library, so adapt as needed.

- Julian

Sent from my smartphone. Sorry about any typos.

On May 2, 2013, at 1:15 AM, Matthew Hooker < "> > wrote:

That's difficult. I've found the easiest way is to put the onus of the dependency on the client of your lwrp

Plaese forgive typos -- sent via phone

On May 1, 2013, at 20:55, Ryan Hass < "> > wrote:

Hello,

I am working on implementing COOK-847, and have encountered a

chicken-and-egg problem. I need to install the certificate_authority

gem; normally I would simply call chef_gem for something like this.

However, since the default recipe is likely to be executed after the

provider I am not able to do this. I also am unable to find a standard

Mixin for chef_gem in Chef 11.x.

What is the correct way to install a gem for Chef to use so I can

require it in my provider?

-Ryan H.

This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify us by e-mail at ( "> ) immediately.

This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify us by e-mail at ( ) immediately.