[chef-dev] Re: RSpec in ChefDK

[Mike < >]

I noticed this as well.

Our current solution is to ensure that people using rspec that comes with omnibus is to have their Ruby environment set to use the ChefDK-supplied one, typically by recommending the addition of the profile-loader line, as recommended by ChefDK's installer:

    eval "$(chef shell-init bash)"

In ~/.profile or such.

Is this perfect? Nope. But it works.

For people that hack on Ruby and are more comfortable with environment mutation (like myself), we leave the env setup to them.

But for most of our team, the env setup is the way to go.

-M

On Wed, May 6, 2015 at 2:40 PM, Noah Kantrowitz < " target="_blank"> > wrote:

Was just working on some slides about ChefDK and noticed that rspec looks like it is still only in the embedded/bin directory, meaning you need to `chef exec rspec`. Most other top-level tools like berks and rubocop are linked in the main bin/ directory so they are available directly, any reason to not do this for rspec?

--Noah