Hi Alvaro; My boxes are stored locally under ~/.vagrant.d/boxes/<box name>/<version>/<provider?>/ Anyway, what should I update there?
On Monday, December 7, 2015 at 2:10:55 AM UTC+2, Alvaro Miranda Aguilera wrote: > > Hello, > > When you import a box, it goes to > > ~/.vagrant.d/boxes/<user>/<box> > > Can you check there? > > You may want to update around that directory. > > Alvaro. > > On Mon, Dec 7, 2015 at 4:35 AM, Gaston <[email protected] <javascript:>> > wrote: > > I would say, instead of at 'provisioning' stage, upon VM creation. > > Those properties cannot be injected after VM has been created. > > In manual deployment, the properties are supplied in a VM deployment > wizard, > > based on the OVF file. > > > > On Sunday, December 6, 2015 at 5:09:29 PM UTC+2, Gaston wrote: > >> > >> Hi all; > >> I am building an automation framework which will deploy customized > boxes > >> using vcloud plugin. > >> I wonder whether Vagrant allows me to supply a VM property which is > >> defined in my OVF file upon provision and not setting it as default > value > >> for this property upon box creation. > >> > >> For example, in my ovf file I have the following currency property: > >>> > >>> <Property ovf:key="currency" ovf:type="string" > >>> ovf:userConfigurable="true" ovf:value="USD - US Dollar".....> > >> > >> > >> Until now I used to override this 'currency' value 'USD' with an > >> alternative supported currency (i.e. EUR) in the ovf file and then > packing > >> this ovf into a Vagrant box. > >> This was a manageable solution until multiple variables appear in my > box > >> (multiple boxes with small ovf file differences). > >> Now I need to create a single box and supply all this variables upon VM > >> provisioning (the values can be supplied in Vagrantfile). > >> > >> Ideas? > > > > -- > > 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] <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/vagrant-up/55f7bbc2-4664-4e14-9c35-74706a89eb71%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/5088c366-5111-4688-afc8-fbd9e1083285%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
