Add support for the AUTHORIZER env variable for LambdaIntegration #1308
Conversation
This file contains 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
…non-proxy) http requests This resolves dherault#816 This replaces dherault#818
|
Thanks @jormaechea , published in v8.7.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Added support for the AUTHORIZER env variable for LambdaIntegration (non-proxy) http requests
Motivation and Context
The
AUTHORIZERenv variable was not working for LambdaIntegration http requests. I just added support for it.This resolves #816
How Has This Been Tested?
I've run the unit tests. Full test run fails even on
masterin my computer.Screenshots (if appropriate):