Re-creating the droplet fails if vagrant up is called immediately vagrant destroy
Closed this issue · 0 comments
viktorbenei commented
The problem seems to be that the plugin doesn't wait for the droplet to be fully deleted.
This causes that if you call vagrant destroy -f and then immediately after it finishes you call vagrant up it'll tell you that the droplet is already created. If you call vagrant up again in like 10 seconds it'll properly start creating the droplet.
A suggestion for the solution: after vagrant destroy this plugin should generate a new ID for the next vagrant create, so that if the previous droplet still under destroy it would be able to create a new droplet, with a new name/id immediately.
Related question: is it possible to manually set a name/ID? We could use that as a workaround in a similar way as I described above.