- From: Hedge Hog <
>
- To:
- Subject: [chef] Invidious choices 101: Chef (<= 0.10) vs Vagrant
- Date: Wed, 30 Mar 2011 18:54:38 +1100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=fkExFxkHsAnYcMnK3tZNJWSRmRR4vJYPFjr447qXQ4lGemsF1xnCu6mJiL4CDalokW 97vxn+eJszK6eh7wZ4ZGmUbzSzJa4VA4/8W9ec3UCR8OunBsJFVt/alS8riEIfr2y9Tp QIps0rFpJIbvDPO937wGDDVlIBzDD01VtEtRg=
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
- [chef] Invidious choices 101: Chef (<= 0.10) vs Vagrant, Hedge Hog, 03/30/2011
Archive powered by MHonArc 2.6.16.