Seems you want to avoid vagrant-chef due those restrictions if that's the case, I would recommend
rsync provisioner to put the files where you need them shell script to run chef command manually. Not ideal, but seems you can't use the default chef provisioner. Alvaro. On Wed, Sep 30, 2015 at 3:45 AM, Moshe Zuisman <[email protected]> wrote: > Additional question. > I thought to bypass those mess by pushing cookbooks to guest machine through > sftp(instead of using synced chef folder). > But - I simply can not prevent Vagrant from attempting to sync chef > cookbooks folder... > When I try to add at chef-solo provisioning "disable chef sync folders: > __________________________________________________________ > config.vm.provision :chef_solo do |chef| > # chef.cookbooks_path = "cookbooks" > chef.synced_folder_type = "rsync" > chef.synced_folder , :disabled true > chef.install = "false" > chef.add_recipe("mfweb") > end > __________________________________________________________ > I get: > >> c:/DevOps/Vagrantfile:36: syntax error, unexpected keyword_true, expecting >> :: or '[' or '.' >> chef.synced_folder , :disabled true >> ^ >> There is a syntax error in the following Vagrantfile. The syntax error >> message is reproduced below for convenience: >> >> c:/DevOps/Vagrantfile:36: syntax error, unexpected keyword_true, expecting >> :: or '[' or '.' >> chef.synced_folder , :disabled true >> ^ >> INFO interface: Machine: error-exit >> ["Vagrant::Errors::VagrantfileSyntaxError", "There is a syntax error in the >> followi >> ng Vagrantfile. The syntax error\nmessage is reproduced below for >> convenience:\n\nc:/DevOps/Vagrantfile:36: syntax error >> , unexpected keyword_true, expecting :: or '[' or '.'\n >> chef.synced_folder , :disabled true \r\n >> ^"] > > Is it possible at all to disable sync of chef cookbooks and copy them to > guest machine manually? > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in violation > of those guidelines may result in your removal from this mailing list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/4d9d0e9b-9b94-4b85-b832-2ce6ad299fbb%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exvQJ7_UCnBgrs2tb0hjJS8ooMXjK3a9V7%3D%3D7S%2B2PqyDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
