Use Chef Workstation's ruby with rbenv #324
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/remove_bundler_version_lock"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The proper way to install Chef, knife, etc. these days is with Chef Workstation.
This adds a local rbenv config for using the bundled workstation ruby in the Chef repo by default. There's a rbenv plugin for this: rbenv-chef-workstation
It also removes the strict bundler version requirement in
Gemfile.lock
, so you can use both newer and older versions of bundler if you want/need.@greg Want to have a quick look at this?
Sure, I will after the call
The changes look good to me but I'm using chruby so I need to find a way to make knife plugins work, with the new setup things like knife-zero don't work when I'm running knife from Chef Workstation. I'll take a closer look tomorrow
I think our
Gemfile
should only containknife-zero
if we use Chef Workstation (everything else is already part of it)chruby's definitely not playing nice with Chef Workstation, even installing a gem directly with
/opt/chef-workstation/embedded/bin/gem install knife-zero
ends up with the gem not being installed in the right path. I think I will end up switching to rbenv to work around this issue, because chruby doesn't appear to have a plugin system, and rbenv-chef-workstation's README mentions a bunch of PATH issues that breaks things in subtle ways.@raucao I forgot to ask, did you check that
knife-zero
works for you with this setup?Yes, of course.
I have a new PR for the RSK cookbook incoming, but it's based on this branch. Would be great if we can merge it soon...
👍
@greg Just for future use: when you add commits to a PR, especially when it's a
kredits-1
, you can add yourself to the assigned-people list, so you also get a full small contrib kredited.