Hello!

I've been working lately with the Azure ARM provider and found that some 
resources can't be properly accesed or managed due to current identification 
including only region/location and id/vmName. Many APIs in AzureARM require 
specifying this resourcegroup and with the current implementation we can only 
manage one resourcegroup for each location.

I think the complete identifier for this provider should include the 
ResourceGroup name (as in scope) so we'd have an identifier such as 
{location/region}/{resourceGroupName/scope}/{vmName/id}

What do you think? I'll be posting a PR soon with these changes but it'd be 
good to have some feedback first since this change would affect the whole 
provider behavior.

Thanks!


Reply via email to