-
Notifications
You must be signed in to change notification settings - Fork 170
How to get current components version? #295
Comments
You can find the uninstall instructions for your platform here: |
You can also find the chef-dk omnibus software definition here: https://github.com/opscode/omnibus-chef/blob/master/config/projects/chefdk.rb |
@brandocorp thanks for those links (especially 2nd one). On Ubuntu 14.04 after running I've also found https://github.com/RoboticCheese/chef-dk-chef which can be used in update scenarios (also implements instructions from https://docs.chef.io/install_dk.html#uninstall) One issue which I can still complain is lack of ability to get components versions in command line. For example |
@brandocorp one more question. In omnibus-chef repo I can't find branch/tag for ChefDK 0.3.5 (latest on https://downloads.chef.io/chef-dk). There is only branch |
I'm not sure how the release/tagging process works for that repo. I'm not seeing a branch or tag for ChefDK 0.3.5, either. You can find the exact details for the omnibus package in the version manifest. It should be under On OSX, mine looks like the following
|
I'm fairly certain this is not an issue in chefdk 0.3.6 |
Heh good timing with new release :) After installing chefdk 0.3.6, I can check all version via exec: $ chef exec berks -v # 3.2.3
$ chef exec kitchen -v # Test Kitchen version 1.3.1
$ chef exec foodcritic -V # foodcritic 4.0.0
$ chef exec rspec -v # 3.1.7
$ chef gem list chefspec | tail -1 # chefspec (4.2.0.beta.1, 4.1.0)
As mentioned in http://lists.opscode.com/sympa/arc/chef/2014-05/msg00150.html we can also check app-bundler gem versions via Closing this, as 0.3.6 release fixes issue for me. |
How can I possibly know what exact versions of components does given ChefDK ships? By components I mean:
chef
cliAfter several updates of ChefDK I have multiple versions of gems installed in ChefDK Ruby env:
Also, when I try to check version by
chef exec kitchen -v
, I'm gettingSo my questions are:
apt-get remove chefdk
leaves all gems apparently. I can image this is desired behavior, but on the other hand, it's not so easy to control gems versions when upgrading ChefDK.The text was updated successfully, but these errors were encountered: