Allow ApiGatewayV2 proxy resources without lambdas #1625
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
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
resourceRoutes.forceconfiguration parameter that enables adding proxies without lambda functions.Motivation and Context
There is no reason that proxies must only be used with lambdas, because they work fine without them.
I use ApiGatewayV2 proxies as a simple proxy layer that does authorization or passes on authorization headers. Problem was that it was not supported by serverless-offline
How Has This Been Tested?
Ran all tests in the repository
Have been using in my projects on a Macbook
All changes are backwards compatible, do not need any changes elsewhere
Screenshots (if appropriate):