Open rbhole opened 1 year ago
Seems the same scenario as #46 the code is testing if the Resource Group exists before using it. It fails because the Azure account does not have permissions to list Resource Groups existing in the Subscription.
@giuliov In azure account I have contributor level access of existing resource group in which I want deploy aggregator function.
That's not enough: you need read permission to list Resource Groups in the Subscription
@giuliov Hi See below screenshot, all access that I have permitted for the resource group,
I gone through Operation returned an invalid status code 'Forbidden' on below command,
.\aggregator-cli.exe install.instance --verbose --name AutoCalculate --resourceGroup myconame-vm-east1 --location "East US"
I used this cli method before in other project and I successfully able to configure. But now I'm facing above issue in different project. The command
.\aggregator-cli.exe logon.azure
where I logon and the command.\aggregator-cli.exe logon.ado
uses two different domain name credentials (e.g. first myname@myorg.com and 2nd myname@myorg-in.com), still above two commands ran properly. Is it possible to create Infrastructure and project is on different domain? Note : I'm using existing resource group that is myconame-vm-east1 while running install.instance command