Fix #1035 - Add apiKeyId to identity information #1169
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
Adds the ApiKeyId to the identity object in the requestContext of the LambdaProxyIntegrationEvent
Motivation and Context
When testing locally it sometimes is needed to read out the apiKeyId instead of the apiKey
#1035
How Has This Been Tested?
I npm link'ed this branch in my local environment and verified the apiKeyId was available in the event.
There seems to be no unit test that covers the contents the identity object, except for a file in the folder called "old-unit". Please let me know if adding an additional expect there is appreciated.
Screenshots (if appropriate):