rbenv_gem resource is not compatible with Chef 13 about ruby_rbenv

[damacus]

I'm going to close this down as I can't reproduce this locally using Chef 14. @javmorin you should be good to upgrade.

This job in Travis installs ruby 2.4.1 can a few gems, and doesn't error like you suggested, so it might be a minor error with the Chef client you're using.

https://travis-ci.org/sous-chefs/ruby_rbenv/jobs/421648868

[damacus]

I'm also surprised it's only the one property that's throwing that error as we purposely mirror all of gem's properties to pass them to gem! :)

[javmorin]

@damacus Thanks for doing that sanity check. I will start rolling out to chef 13 with the current version of the cookbook and if something comes up, I will file a new bug. It is puzzling that they would make a big deal about a deprecation but in the end nothing happens. I had assumed that things would break as indicated and wasn't able to verify it myself (kitchen run was taking >60 minutes to run).

[aried3r]

Not a maintainer, but the README states that this cookbook requires Chef 13+, so this is expected. I'm not sure if there'll be any additional work for Chef 12.

[damacus]

Closing as Chef-12 isn't a supported platform. That's our fault for not upping the version.

I've released 2.1.0to make this clearer.

Apologies for the understanding.

[javmorin]

@aried3r @damacus I realize that Chef 12 is no longer supported. I had not been able to upgrade to Chef 13 because the current version of this cookbook was warning as above, and indicating it would fail with an exception if run on Chef 13. Does 2.1.0 fix this broken issue?

[damacus]

Ouch, a 60 minute run. How many rubies are you installing?

[javmorin]

This was running test kitchen for ruby_rbenv. I suspect I need to make some tweaks to my vagrant/virtualbox config to have it run better (my dev PC is in serious need of an upgrade as well)

[damacus]

If you have any troubles don't hesitate to drop in on #sous-chefs in the chef community slack if you need anymore help! 👍

[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.