Lambda-Event-Path-and-Resource-Sync #1137
Merged
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
Change LambdaProxyIntegrationEvent returned resource to use non-stagePrepended URL from instance #path intead of route.path.
Motivation and Context
When running serverless-offline locally, the LambdaProxyIntegrationEvent uses the route.path to define the event.resource instead of this.#path. When using stages prepended to URLs to keep in step with a multi-environment local development setup (i.e. multiple environments tested with Postman), it is desirable to have the stage prepend the endpoint URL, but not desirable for the stage to mutate the event.resource where router / controller logic is determined.
Fixes: #1029
How Has This Been Tested?
Ran AWS Lambdas locally with URLs prepended by Stage with Postman.