Deletion of Azure resources does not delete the deployment itself

[Michael Nelson]

The function `deleteResourceGroup` , in the case of an existing resource group not created by packer, goes ahead and deletes the resources associated with the deployment (great), but does not delete the historical deployment itself.

This is not an issue until you hit Azure's limit of 800 deployments in a resource group (which in a CI situation is not hard). I was wondering if it's intentional that the historical record is left around in this case - if not, I'll create an issue. Given that it is deleted (automatically) in the case where packer creates the resource group, I don't see why it shouldn't be deleted in this case (it's the same historical artifact of the build).

Thanks for any info!