-
Notifications
You must be signed in to change notification settings - Fork 157
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 Update-VSTeamUserEntitlement to correctly use contentype application/json-patch+json #430
Fix Update-VSTeamUserEntitlement to correctly use contentype application/json-patch+json #430
Conversation
@SebastianSchuetze - PR raised. Can you take it fwd from here? |
@thahif could you check that you allowed me to make updates in your branch as a maintainer? Otherwise you would need to update the changelog.md in the same way like the other entries. Your change would fit in version 7.5.0 |
@SebastianSchuetze - I see that you can edit my branch. |
Strange. I can't edit the branch. |
@SebastianSchuetze - what do we next? I have re-applied that allow edit by maintainers permission. Can you please check? |
If not then I will use your branch in one of mine and merge that one. This I would close then. |
@SebastianSchuetze - Any timeline that you can comment when this will be available to download? |
I will try my best but first I need to solve this #424 and it is usually happening outside of my worktime. So no ETA I can only try to give my best. Even if I merge it it will not be available before release works. |
But you might want to check the cmdlet Invoke-VSTeamRequest which allows you to address any API of AzDO with your own custom JSON body. In that way you might have a work around in the mean time. You just need to handle the API yourself a bit. Or even copy the code and reuse it with this command. |
I solved finally the problem with the workflow.... or at least nearly. I will be working on your PR and merge it as soon as possible. |
PR Summary
PR Checklist