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

[Issue] azd pipeline config results in role assignment error #2287

Closed
1 task done
pamelafox opened this issue May 22, 2023 · 4 comments · Fixed by #2288
Closed
1 task done

[Issue] azd pipeline config results in role assignment error #2287

pamelafox opened this issue May 22, 2023 · 4 comments · Fixed by #2288
Labels
needs-triage For new issues

Comments

@pamelafox
Copy link
Member

Output from azd version

azd version 0.9.0-beta.3 (commit e564b12)

Describe the bug

When I try to configure my pipeline, I get an error:

flask-db-quiz-example % azd pipeline config

Configure your GitHub pipeline


ERROR: role assignment with scope '/subscriptions/32ea8a26-5b40-4838-b6cb-be5c89a57c16' was not found

To Reproduce

It's happening for me on https://github.com/pamelafox/flask-db-quiz-example/ but I don't know if it will happen for others.

Expected behavior

Usually config works.

Environment

Mac OS X M1

@ghost ghost added the needs-triage For new issues label May 22, 2023
@pamelafox
Copy link
Member Author

Update: It's happening in other repos as well now.

@weikanglim
Copy link
Contributor

Our team is taking a look.

@weikanglim
Copy link
Contributor

@pamelafox

Do you mind running the following command, and see if you get non-empty results?

az role assignment list --scope /subscriptions/32ea8a26-5b40-4838-b6cb-be5c89a57c16 --assignee <your logged in user email> --include-groups

@pamelafox
Copy link
Member Author

?1simple-flask-server-example % az role assignment list --scope /subscriptions/32ea8a26-5b40-4838-b6cb-be5c89a57c16 --assignee pamelafox@microsoft.com --include-groups
[]

@ellismg ellismg mentioned this issue May 22, 2023
ellismg added a commit that referenced this issue May 22, 2023
The intention of this change was to try to do some up front checking
for cases where we knew pipeline config was likely to fail. We've
discovered that this logic was faulty, and so we're rolling the change
back for now.

Fixes #2287
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage For new issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants