Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting deployment in a resource group doesn't delete the resources in the deployment #797

Closed
lyan-git opened this issue Sep 21, 2016 · 5 comments
Labels
ARM question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@lyan-git
Copy link

I opened this issue #585 regarding a while ago and we still feel strongly that resource_client.deployments.delete() should delete the resources under the deployment just as delete resource group does .
We have a case where we have a vnet that contains a load balancer with multiple gateways attached to it. The load balancer and the gateway need to be within one resource group. So we have a resource group that contain both load balancer deployment and multiple gateway deployments.
Now if the user want to delete one gateway only, we try to delete deployment logic entity rather than delete the whole resource group which will delete both load balancer and all gateway deployments. T hen we are facing the fact that the resources under deployment are not deleted. Do we need to delete those resources one by one throughout deployment? If we can create a deployment in one template, why can't we delete the deployment template resources at one time just like resource group? I thought the delete deployment should bring in that function.

Thanks.
Li

@lmazuel lmazuel added ARM question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 21, 2016
@lmazuel
Copy link
Member

lmazuel commented Sep 21, 2016

Hi @lyan-git

Unfortunately, I can't help you right now, this is not really a Python issue :(
I can cite here the same people as in #585 if you like, to still continue the discussion. And send your issue by email at the ARM team.
Thanks, sorry to be not really helpful....

@lyan-git
Copy link
Author

lyan-git commented Sep 21, 2016

Thanks Laurent! I couldn’t find a way to reopen that case, seems I didn’t get the response back, wonder if there is another category I can open the case.

@lmazuel
Copy link
Member

lmazuel commented Sep 21, 2016

On Github, you can open the issue here: https://github.com/Azure/azure-rest-api-specs
It will be cross-language and not Python specific, and easier to get the right person to answer.

@lyan-git
Copy link
Author

lyan-git commented Sep 21, 2016

Will do, thanks! You can close this issue then.

@lmazuel
Copy link
Member

lmazuel commented Sep 21, 2016

Ok, thank you for your support!

@lmazuel lmazuel closed this as completed Sep 21, 2016
@bsiegel bsiegel added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 26, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ARM question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants