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

Support activation of multiple roles via scope name #214

Open
robalexj opened this issue Oct 18, 2024 · 1 comment
Open

Support activation of multiple roles via scope name #214

robalexj opened this issue Oct 18, 2024 · 1 comment

Comments

@robalexj
Copy link

Found this really useful, thanks for your efforts. It would be great if it could activate multiple roles via the scope_name rather than the scope itself. The example here suggests is possible, however scope_name is not parsed, instead scope is required: https://github.com/demoray/azure-pim-cli?tab=readme-ov-file#example-usage-2

@demoray
Copy link
Owner

demoray commented Oct 25, 2024

Thanks for the feedback!

I agree your proposed feature would be useful. I will need to wait on this for a bit as something is currently wrong on the Azure side. During my investigation to address this feature, Azure started returning role definitions without scope names.

This is apparently causing issues in the portal as well, as I cannot see eligible roles and I see the following exception in my browser console:

[Microsoft_Azure_PIMCommon]  5:22:57 PM CustomErrorLog CustomErrorLog: message: n.roleDefinition(...).resource(...).displayName is not a function
name: TypeError
stack: TypeError: n.roleDefinition(...).resource(...).displayName is not a function

I will try to investigate this over the next week, as this might be a transient issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants