You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Found this really useful, thanks for your efforts. It would be great if it could activate multiple roles via the
scope_name
rather than thescope
itself. The example here suggests is possible, howeverscope_name
is not parsed, insteadscope
is required: https://github.com/demoray/azure-pim-cli?tab=readme-ov-file#example-usage-2The text was updated successfully, but these errors were encountered: