Possible bug in Custom Commands Azure deployment scripts?

[dargilco]

For a long time, I could not deploy the Custom Commands (CC) demo on my work machine. It failed with some error and gave the name of a resource group that I did not know where it came from (it was not the one I supplied in the script command line). After investigating, I found out how to fix it: I had some Azure configuration defaults (see this link for more info Azure CLI configurations) You can see those by typing " az configure -l ”. I had a default name for resource group, and that was the name that appeared when my CC deployment script failed. After clearing these settings (editing "C:\Users\<>\.azure\config" to delete the relevant configuration), the CC deployment script worked. For some reason, the deployment script picked up the Azure default I had set on this PC and ignored the resource group name I provided as command line argument.
I'd like to investigate this further, as others may hit this issue. Logging this as a GitHub issue so we don't forget and in case someone else hits this.