The function `deleteResourceGroup` <https://github.com/hashicorp/packer/blob/master/builder/azure/arm/step_delete_resource_group.go#L34> , 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! -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/ed97ea95-1ab0-4bf5-9f93-fb6e29d6c04c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
