Hi,

They are in separate files, in separate repositories. It looks like I’m going 
to have to write a tool—maybe an excuse to learn go!
Is there any other solution, would this be something that would be wanted in 
vagrant?
Cheers
Sean.

From: vagrant-up@googlegroups.com [mailto:vagrant-up@googlegroups.com] On 
Behalf Of Alvaro Miranda Aguilera
Sent: 15 September 2016 13:44
To: vagrant-up@googlegroups.com
Subject: Re: [vagrant-up] Dependency between vm's in development

Hello,

Vagrantfile is read top to bottom. Virtualbox is not run on parallel, so you 
can try:

say web requires db

you can do


db

web

and will work

Thanks
Alvaro.


On Thu, Sep 15, 2016 at 11:31 AM, Sean Farrow 
<sean.far...@tendosolutions.com<mailto:sean.far...@tendosolutions.com>> wrote:
Hi all,

Within a local environment I have a windows vm, created with packer that 
depends on a Linux vm running Redis to function.
Is there a way of telling vagrant that one vm depends on another?
How have others solved the problem. In production this is fine, as we are using 
Terraform and this will order resource creation.
Any help appreciated.
Kind regards
Sean.
--
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 
vagrant-up+unsubscr...@googlegroups.com<mailto:vagrant-up+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/VI1PR0201MB2013B9E1D47420FACA3610AB83F00%40VI1PR0201MB2013.eurprd02.prod.outlook.com<https://groups.google.com/d/msgid/vagrant-up/VI1PR0201MB2013B9E1D47420FACA3610AB83F00%40VI1PR0201MB2013.eurprd02.prod.outlook.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro
(+31)103400555
--
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 
vagrant-up+unsubscr...@googlegroups.com<mailto:vagrant-up+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezMcn1ORvfpJsBQZ%2BVELz8FmEYkpLixFG3k-o-u%3DyJaLw%40mail.gmail.com<https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezMcn1ORvfpJsBQZ%2BVELz8FmEYkpLixFG3k-o-u%3DyJaLw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/VI1PR0201MB2013A0887A2014995BAB339E83F00%40VI1PR0201MB2013.eurprd02.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to