Closed ddelnano closed 3 years ago
I validated that this isn't the case on the latest version of the provider (v0.15.0) and also that there is an acceptance test that was written before this issue that should prevent this. So I'm not sure how this happened, closing. It can be investigated more if there are future occurrences of it.
When a VM is destroyed but still exists in the statefile the provider will show the following error
The expected behavior is that the provider will realize the resource is missing and will attempt to recreate it.