Deleting Static Web App from within VS Code leaves behind Azure Resource Groups
To Reproduce
Use VS Code to checkin code to Github with action to deploy to new Azure Static Web App
After successful build and deployment...
Go to Azure Portal and see that a dedicated resource group was created for the static web app
In VS Code, use the Static Web App plugin to delete the Static Web App
Go back to Azure portal and see that the dedicated resource group remains.
Expected behavior
I think this should be handled differently. Basically what I saw after a number of trial and error failed deployments and deleting the static web apps from within VS Code, my Azure portal had many resource groups with auto-incremented names. In practice these would leave a person unsure which was still in use and which weren't
Transferring the issue from Static Web Apps #676 by @SheldonHage
Deleting Static Web App from within VS Code leaves behind Azure Resource Groups
To Reproduce
Expected behavior I think this should be handled differently. Basically what I saw after a number of trial and error failed deployments and deleting the static web apps from within VS Code, my Azure portal had many resource groups with auto-incremented names. In practice these would leave a person unsure which was still in use and which weren't