Re: [PROPOSAL] Azure ARM shared resource group

The link you posted to creates a "default" network (yes presumably with a resource group) but it should only do this if the default network doesn't exist and it should then leave the network there for the next-time you use the same azure region. See here for a description of this behaviour

Re: [PROPOSAL] Azure ARM shared resource group

Duncan. jClouds does the right thing and remove the resource group when we release the machine, the issue is definitely in Brooklyn (see my previous link): Brooklyn always creates a shared resources group, multi-vm deployment or not, and we never remove it. The jClouds issue you referenced is

Re: [PROPOSAL] Azure ARM shared resource group

Thomas, Sorry - wrong url - should have been https://issues.apache.org/jira/browse/JCLOUDS-1331 Duncan On Thu, 12 Apr 2018 at 15:27 Duncan Grant wrote: > Thomas, > > I think this problem is in jclouds as is does try to remove the resource > group but fails due to

Re: [PROPOSAL] Azure ARM shared resource group

Thomas, I think this problem is in jclouds as is does try to remove the resource group but fails due to caching on the api making it look like the resource group is not empty. See