fix: explicitly lookup AWS_ENDPOINT_URL_LAMBDA while using preview lambda model#22
Merged
fix: explicitly lookup AWS_ENDPOINT_URL_LAMBDA while using preview lambda model#22
Conversation
bchampp
force-pushed
the
fix/lambda-client-env-var
branch
from
d147b0c to
e3eac14
Compare
anthonyting
approved these changes
Oct 7, 2025
ketpatel1998
approved these changes
Oct 7, 2025
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
3 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.
Description of changes:
Since we're using a custom
lambdainternalmodel during development, the functionality to matchAWS_ENDPOINT_URL_LAMBDAwasn't working properly and our checkpoint calls weren't hitting the backend.Tested it by building the python SDK and running an example against the backend.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.