When running first vagrantfile network settings are honored while uploading template and template is assigned to corresponding network.
When running next vagrant file using same template setting (don't want template twice on disk ;-) ) but different betwork it finds and uses the already uploaded template.
On vm deployment the new network settings are not applied
Yes, I was looking at this specific behavior last night, there's a bug in the big PR that was part of the 0.2.0 release. I will mark this as a duplicate of #6 and track it over there.
Think this is somehow related to issue #6
When running first vagrantfile network settings are honored while uploading template and template is assigned to corresponding network.
When running next vagrant file using same template setting (don't want template twice on disk ;-) ) but different betwork it finds and uses the already uploaded template.
On vm deployment the new network settings are not applied