Use full class name for rvm_environment resource usage inside Chef::Provider::Package:RVMRubygems class

[nomadium]

I propose this change because the cookbook was not working with Chef 12.0.0. I also tested it with previous versions and works as expected.

This should fix: #283.

[akshah123]

👍 since it is a known deprecated functionality now. For refrence: chef/chef#2591

[martinisoft]

Hiya @nomadium

Can you confirm if this change also breaks Chef 11 compatibility? I am fine with breaking Chef 10 at this point, but Chef 11 and 12 both should be supported until the 2.x release.

[nomadium]

Hi @martinisoft.

I confirm you I tested this change with 11.16.4 and 12.0.0 and it worked.

[alambike]

👍 Works ok in Chef 12.0.3

[mshappe]

👍 I just tested this by pulling the branch in via my Berksfile, and it seemed to behave much better, now! Someone ought to merge this! 😄

[nimeshsubramanian]

@martinisoft and @cmluciano would love to see this released.

[ryancragun]

@martinisoft @cmluciano +1 for a release with this fix!

[tagomoris]

Are there any plan to release this fix?

[trinitronx]

It would seem that this fix is going to be incorporated into version 0.10.1 according to the CHANGELOG. If you are using Berkshelf to manage your cookbook dependencies, you can test out the unreleased new version by specifying a commit after #284 was merged in your Berksfile. That means any commit after: e840e576e05bd0e815f1080988e57d1182068f78 should work. However, do check the changelog, because it lists that potential breaking changes were made.

For example, if I wanted to test out that commit I put this in my Berksfile:

cookbook 'rvm', :github => 'martinisoft/chef-rvm', :ref => 'e840e576e05bd0e815f1080988e57d1182068f78'

See the Berkshelf Documentation for more supported syntax reference.

Then just run: berks update rvm && berks install, test it out perhaps with test-kitchen, vagrant, or chef-solo however you want. Then upload to chef server with berks upload rvm & deploy out to infrastructure nodes with chef-client.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.