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

Fix azuread_privileged_access_group_eligibility_schedule resource update functionality #1614

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

h0597
Copy link

@h0597 h0597 commented Jan 9, 2025

My goal with this pull request is to improve the azuread_privileged_access_group_eligibility_schedule resource.

Updating the 'Update' functionality to use the adminUpdate instead of adminAssign As per Microsoft graph documentation

adminUpdate: For administrators to change existing eligible assignments. instead of adminAssign: For administrators to assign group membership or ownership eligibility to principals.

I found this issue in relation to this problem: #1412

As this is my first fork pull request, I hope this way is correct to do it. If not, please let me know so I can improve the pull request.

Updating the Update functionality to use the adminUpdate: For administrators to change existing eligible assignments. instead of 
adminAssign: For administrators to assign group membership or ownership eligibility to principals. As per microsoft graph documentation
@SPALLADI
Copy link

Any luck with merging the PR?

@relent0r
Copy link

I'm interested in this one too as I've hit the issue where you get 400 errors and are unable to apply after any changes are required. I need to manually delete all the assignments and reapply to make it work which given how slow the azure interface is for this is really painful.

@farflungfish
Copy link

This is definitely the solution we are looking for; total pain in the rear without it at the moment having to recreate role assignments.

@xzuttz
Copy link

xzuttz commented Jan 27, 2025

An issue for us as well. Looking forward to a solution soon.

@srjennings
Copy link

PR is ready for review, folks are looking for review/merge status
CC @katbyte @jackofallops

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

Successfully merging this pull request may close these issues.

6 participants