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.
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
Include params set in provide-client-param event handlers in dynamic context params for endpoint resolution #2920
Include params set in provide-client-param event handlers in dynamic context params for endpoint resolution #2920
Changes from 2 commits
8b4afd2
dd41560
bd44524
763d1f7
e4c89a5
878cd84
d8ed89d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this could be called from within
_resolve_endpoint_ruleset
at the very start of it? I'm thinking in purely organizational terms just because_make_api_call
is a rather long, complex function already.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only concern I have with this PR is we're moving this into multiple places now making any future changes harder to keep consistent.
It would be nice to keep these consolidated with
_convert_to_request_dict
, but I don't see an immediate solution for that.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think using my suggestion of putting this in
_resolve_endpoint_ruleset
would accomplish that no?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or does this still need to happen immediately after endpoint resolution for presigned URLs?