Well i gave up on trying to run Chef via the provisioning and used the
shell provisioning. Basically, upload my script file and run myself.
config.vm.provision 'file', source: 'myfile.rb', destination:
'/tmp/myfile.rb'
config.vm.provision 'shell', name: 'Run Chef Recipe', privileged: true,
inline: <<-SHELL
sudo su - -c 'chef-apply /tmp/myfile.rb'
SHELL
I don't know whether this is a problem with Vagrant but more likely
Microsoft just being Microsoft and not being that open.
At the end of the day I do have a 'generic' vagrant file that works for
optional providers but the lesson is that most things that seems to work
for Oracle VB etc don't work on Azure..
Thanks
Mark
--
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/58a5087a-c852-4411-a468-a23901ea27c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
