Added support for AUTHORIZER env var in lambda integration (v6) #818
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
jormaechea
changed the title
|
hey @jormaechea thank you for this PR as well! Gonna look over this later today. |
|
Is this still active @dnalborczyk / @jormaechea ? I'd like to be able to use the AUTHORIZER variable in a non-proxy integration. |
jormaechea
added a commit
to jormaechea/serverless-offline
that referenced
this pull request
Nov 28, 2021
…non-proxy) http requests This resolves dherault#816 This replaces dherault#818
|
Replaced by #1308 |
jormaechea
deleted the
Issue-816-Authorizer-env-var-in-lambda-integration-v6
branch
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.
Fixes #816 for v6