Conversation
… exists -> GetOrCreate, update hooks
das-Abroxas
approved these changes
Apr 19, 2024
Contributor
das-Abroxas
left a comment
das-Abroxas
left a comment
There was a problem hiding this comment.
This behavior is much better for users if they really only have to register at a proxy once instead with each of his authorization tokens individually. Good work 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This small upgrade fixes an regression in the pre-signed URL handler.
Previous iterations had a GetOrCreate method for fetching Credentials from a proxy. This was changed during the 2.0 update resulting in an unauthorized error when making a Get call before a create call.
This update reverts this behavior on the server site.
It also simplifies and removes some unnecessary redundancy in the hook handling logic.