Closed matudose closed 2 months ago
Need to hold on this. May have found a bug in AuthorizationManager API. Roles requested from it don't appear to match data as shown in vCenter UI.
[like] Matei Tudose reacted to your message:
From: Eugene Tolmachev @.> Sent: Friday, July 26, 2024 2:45:37 PM To: Azure/Microsoft.AVS.Management @.> Cc: Matei Tudose @.>; State change @.> Subject: Re: [Azure/Microsoft.AVS.Management] add remove-customrole function (PR #230)
Merged #230https://github.com/Azure/Microsoft.AVS.Management/pull/230 into main.
— Reply to this email directly, view it on GitHubhttps://github.com/Azure/Microsoft.AVS.Management/pull/230#event-13662363488, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOY2G7BBV7OIJJ2VSL3WL7DZOJOJDAVCNFSM6AAAAABKSYNLBGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGY3DEMZWGM2DQOA. You are receiving this because you modified the open/close state.Message ID: @.***>
This PR closes #
The changes in this PR are as follows:
Add a Remove-Customrole function which would allow a customer who inadvertently created a role with too many privileges to remove it
I have read the contributor guidelines and have completed the following:
AVSAttribute
to newly exported functions.