[chef] Re: Managing dependencies via Berkshelf

[Tim Green < >]

Did you try removing the depends line from the metadata.rb?  That shouldn't be required, especially if you're explicitly declaring it in the Berksfile so that it can be downloaded from your local Chef server.

From: Aleksandr Chumakov < "> >
Reply-To: " "> " < "> >
Date: Monday, August 12, 2013 10:14 AM
To: " "> " < "> >
Subject: [chef] Managing dependencies via Berkshelf

Hi, 

I have a question about Berkshelf and dependency management (sorry, maybe it's silly).

I've written cookbook my_nginx which depends on cookbook nginx that is located on our production chef-server. I want to use Vagrant + Berkshelf for testing it.

So i wrote in metadata.rb

depends "nginx"

and in Berksfile 

metadata
cookbook 'nginx', chef_api: :config

When i execute berks install, i get cookbook from our Chef server in ~/.berkshelf/cookbooks/nginx-1.7.0. However, when i use vagrant up it downloads dependency from https://cookbooks.opscode.com/api/v1/ to ~/.berkshelf/default/vagrant/berkshelf-20130812-xxxxx and there are absent some recipes i need.

What I need to do for downloading dependencies from my Chef server when i use vagrant?

Additional info:

Vagrant version 1.2.7

Berkshelf (2.0.6)

vagrant-berkshelf (1.3.2)

$ vagrant plugin list

vagrant-berkshelf (1.3.3)

vagrant-omnibus (1.1.0)

My ~/.berkshelf/config.json

{
  "chef":{
    "chef_server_url":"http://api.chef.organization.com",
    "validation_client_name":"chef-validator",
    "validation_key_path":"/home/user/.chef/validation.pem",
    "client_key":"/home/lexx/.chef/user.pem",
    "node_name":"user"
  },
  "vagrant":{
    "vm":{
      "box":"Centos_chef11",
      "box_url":"http://vagrant.server/vagrant_berkshelf.box",
      "forward_port":{
      },
      "network":{
        "bridged":false,
        "hostonly":"33.33.33.10"
      },
      "provision":"chef_solo"
    }
  },
"ssl":{
    "verify":true
  }
}

Thanks!

Please excuse my bad English.