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

Operation returned an invalid status code 'Forbidden' #276

Open
rbhole opened this issue Jan 27, 2023 · 4 comments
Open

Operation returned an invalid status code 'Forbidden' #276

rbhole opened this issue Jan 27, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@rbhole
Copy link

rbhole commented Jan 27, 2023

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"
Autocal

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 [email protected] and 2nd [email protected]), 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

@rbhole rbhole added the bug Something isn't working label Jan 27, 2023
@giuliov
Copy link
Member

giuliov commented Jan 28, 2023

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.

@rbhole
Copy link
Author

rbhole commented Jan 30, 2023

@giuliov In azure account I have contributor level access of existing resource group in which I want deploy aggregator function.

@giuliov
Copy link
Member

giuliov commented Jan 30, 2023

That's not enough: you need read permission to list Resource Groups in the Subscription

@rbhole
Copy link
Author

rbhole commented Jan 30, 2023

@giuliov Hi See below screenshot, all access that I have permitted for the resource group,
Autocal3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants