ChefDK with Berkshelf 3.2.4


#1

Hello,

I am using using Berkshelf 3.2.3 via ChefDK 0.5.1. There is a bug in
Berkshelf discussed here:


And fixed here:

It looks like the pull request was merged in January, and Berkshelf was
bumped to 3.2.4 on April 30 (12 days ago). When will a new version of
ChefDK be released that brings in Berkshelf 3.2.4? In the meantime I have
modified my local berksfile.rb to fix this, but it would be nice if there
was a new ChefDK release to address this.

Kyle


#2

Kyle:

If you’ve got your $PATH configured to pick up gems installed into Chef’s embedded Ruby (like so: $HOME/.chefdk/gem/ruby/2.1.0/bin:/opt/chefdk/bin:$PATH), you can just chef gem install berkshelf to update the gem to the latest.


Jeff Byrnes
@thejeffbyrnes
Lead DevOps Engineer
EverTrue
704.516.4628

On May 12, 2015 at 3:09:03 PM, Kyle Morgan (kyle.n.morgan@gmail.com) wrote:

Hello,

I am using using Berkshelf 3.2.3 via ChefDK 0.5.1. There is a bug in Berkshelf discussed here:


And fixed here:

It looks like the pull request was merged in January, and Berkshelf was bumped to 3.2.4 on April 30 (12 days ago). When will a new version of ChefDK be released that brings in Berkshelf 3.2.4? In the meantime I have modified my local berksfile.rb to fix this, but it would be nice if there was a new ChefDK release to address this.

Kyle


#3

I understand. Unfortunately, vagrant-berkshelf (4.0.3) complains if you are
not using berkshelf via ChefDK.

Kyle

On Tue, May 12, 2015 at 3:15 PM, Jeff Byrnes jeff@evertrue.com wrote:

Kyle:

If you’ve got your $PATH configured to pick up gems installed into Chef’s
embedded Ruby (like
so: $HOME/.chefdk/gem/ruby/2.1.0/bin:/opt/chefdk/bin:$PATH), you can just
chef gem install berkshelf to update the gem to the latest.


Jeff Byrnes
@thejeffbyrnes http://twitter.com/thejeffbyrnes
Lead DevOps Engineer
EverTrue http://www.evertrue.com/
704.516.4628

On May 12, 2015 at 3:09:03 PM, Kyle Morgan (kyle.n.morgan@gmail.com)
wrote:

Hello,

I am using using Berkshelf 3.2.3 via ChefDK 0.5.1. There is a bug in
Berkshelf discussed here:

https://github.com/berkshelf/vagrant-berkshelf/issues/237
https://github.com/berkshelf/berkshelf/pull/1342

And fixed here:

https://github.com/berkshelf/berkshelf/pull/1380

It looks like the pull request was merged in January, and Berkshelf was
bumped to 3.2.4 on April 30 (12 days ago). When will a new version of
ChefDK be released that brings in Berkshelf 3.2.4? In the meantime I have
modified my local berksfile.rb to fix this, but it would be nice if there
was a new ChefDK release to address this.

Kyle


#4

Whoops, I previously replied without reading your entire comment.

This does indeed fix the problem without manually editing files. However,
it would still be nice to have ChefDK ship with the latest version of
berkshelf.

Kyle

On Tue, May 12, 2015 at 3:15 PM, Jeff Byrnes jeff@evertrue.com wrote:

Kyle:

If you’ve got your $PATH configured to pick up gems installed into Chef’s
embedded Ruby (like
so: $HOME/.chefdk/gem/ruby/2.1.0/bin:/opt/chefdk/bin:$PATH), you can just
chef gem install berkshelf to update the gem to the latest.


Jeff Byrnes
@thejeffbyrnes http://twitter.com/thejeffbyrnes
Lead DevOps Engineer
EverTrue http://www.evertrue.com/
704.516.4628

On May 12, 2015 at 3:09:03 PM, Kyle Morgan (kyle.n.morgan@gmail.com)
wrote:

Hello,

I am using using Berkshelf 3.2.3 via ChefDK 0.5.1. There is a bug in
Berkshelf discussed here:

https://github.com/berkshelf/vagrant-berkshelf/issues/237
https://github.com/berkshelf/berkshelf/pull/1342

And fixed here:

https://github.com/berkshelf/berkshelf/pull/1380

It looks like the pull request was merged in January, and Berkshelf was
bumped to 3.2.4 on April 30 (12 days ago). When will a new version of
ChefDK be released that brings in Berkshelf 3.2.4? In the meantime I have
modified my local berksfile.rb to fix this, but it would be nice if there
was a new ChefDK release to address this.

Kyle


#5

Well, I’m glad to hear that! And Chef DK can only ship as fast as it does. It will always lag slightly behind one tool or another. They work hard to try & keep up though!


Jeff Byrnes
@thejeffbyrnes
Lead DevOps Engineer
EverTrue
704.516.4628

On May 12, 2015 at 3:24:12 PM, Kyle Morgan (kyle.n.morgan@gmail.com) wrote:

Whoops, I previously replied without reading your entire comment.

This does indeed fix the problem without manually editing files. However, it would still be nice to have ChefDK ship with the latest version of berkshelf.

Kyle

On Tue, May 12, 2015 at 3:15 PM, Jeff Byrnes jeff@evertrue.com wrote:
Kyle:

If you’ve got your $PATH configured to pick up gems installed into Chef’s embedded Ruby (like so: $HOME/.chefdk/gem/ruby/2.1.0/bin:/opt/chefdk/bin:$PATH), you can just chef gem install berkshelf to update the gem to the latest.


Jeff Byrnes
@thejeffbyrnes
Lead DevOps Engineer
EverTrue
704.516.4628

On May 12, 2015 at 3:09:03 PM, Kyle Morgan (kyle.n.morgan@gmail.com) wrote:

Hello,

I am using using Berkshelf 3.2.3 via ChefDK 0.5.1. There is a bug in Berkshelf discussed here:


And fixed here:

It looks like the pull request was merged in January, and Berkshelf was bumped to 3.2.4 on April 30 (12 days ago). When will a new version of ChefDK be released that brings in Berkshelf 3.2.4? In the meantime I have modified my local berksfile.rb to fix this, but it would be nice if there was a new ChefDK release to address this.

Kyle