[chef] Re: Invidious choices 101: Chef (<= 0.10) vs Vagrant

[Tim Diggins < >]

What do you mean by "using vagrant and chef in the same project". I'm using chef as a provisioner (primarily as a means to test my chef recipes/roles in a speedy environment (switching vagrant between a chef-solo (for speed) and chef server model (to the platform, for testing more advanced configs). But I don't think that's what you meant. (I notice that vagrant during a "vagrant provision" run seems to use an earlier version of chef than the  latest one I have installed - is gem dependency management that clever?)

Tim

On Wed, Mar 30, 2011 at 8:54 AM, Hedge Hog < " target="_blank"> > wrote:

Hi,
Due to Chef pinning the json gem at <=1.4.6 you can't use vagrant in
the same ruby gem environment as Chef....
This issue is proving to be a blocker in the quest to reuse Cucumber
steps in Vagrant+Chef use cases.

What methods are people adopting to use Chef and Vagrant in the same project?

At the moment all I can think of is to try switch gemsets with RVM
whenever you need to use `knife ...`, but I'm open to any other
suggestions
Specifically, I see the current master still has Chef pinning json gem
at <=1.4.6. So I assume this restriction will be around for some
considerable time. That means any workaround that is not clean/easy
gets a look in :)

Appreciate any hints or tips.

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
  Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com