David Justice
David Justice
I see what's going on. It's reading the ssh info rather than looking for winrm. I'll try to replicate.
I believe the change would land in a few places: - The outward facing provider configuration to allow folks to add plan information in the vagrant file: - https://github.com/Azure/vagrant-azure/blob/v2.0/lib/vagrant-azure/config.rb -...
Makes sense.
Is this still the case? Could you share your Vagrantfile (minus the sensitive info)?
Could a reasonable response to this be, please use 2.0.0.pre2 or greater?
Last I investigated this, that is exactly what I found @matt-richardson. The lease on the disk took too long to release and we give up trying to delete it. I...
I think this could be added pretty simply through https://github.com/Azure/azure-storage-ruby/blob/master/lib/azure/storage/blob/blob.rb#L571.
My first inclination is to delete the deployment on when we receive the error in provisioning, but that might be painful since you will have no way to dig into...
I think the right way to do this is to tag the resources uniquely and destroy only those tagged resources we create. It will take a bit to add this,...
@codestothestars, this module (https://github.com/Azure/vagrant-azure/blob/v2.0/lib/vagrant-azure/util/machine_id_helper.rb) provides the functionality for serializing / de-serializing the persisted machine identifier. Vagrant persists this to disk in the local directory in the .vagrant directory. Specifically, under...