fix(apigatewayv2-authorizers): incorrect identitySource default for WebSocketLambdaAuthorizer#18315
Merged
mergify[bot] merged 2 commits intomasterfrom Jan 7, 2022
Merged
fix(apigatewayv2-authorizers): incorrect identitySource default for WebSocketLambdaAuthorizer#18315mergify[bot] merged 2 commits intomasterfrom
identitySource default for WebSocketLambdaAuthorizer#18315mergify[bot] merged 2 commits intomasterfrom
Conversation
|
|
identitySource default for WebSocketLambdaAuthorizer
otaviomacedo
approved these changes
Jan 7, 2022
Contributor
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
TikiTDO
pushed a commit
to TikiTDO/aws-cdk
that referenced
this pull request
Feb 21, 2022
… `WebSocketLambdaAuthorizer` (aws#18315) We introduced `WebSocketLambdaAuthorizer` in aws#16886 with an incorrect default `identitySource`, according to these [docs](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigatewayv2-authorizer.html#cfn-apigatewayv2-authorizer-identitysource). The result is that using the default `identitySource` results in a deploy-time failure. This PR fixes the error and adds documentation for the syntax for all `identitySource` possibilities. I can confirm that this default successfully passes `cdk deploy` on my local app. Fixes aws#18307. BREAKING CHANGE: `WebSocketLambdaAuthorizerProps.identitySource` default changes from `['$request.header.Authorization']` to `['route.request.header.Authorization']`. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This file contains hidden or 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
3 participants
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.
We introduced
WebSocketLambdaAuthorizerin #16886 with an incorrect defaultidentitySource, according to these docs. The result is that using the defaultidentitySourceresults in a deploy-time failure.This PR fixes the error and adds documentation for the syntax for all
identitySourcepossibilities.I can confirm that this default successfully passes
cdk deployon my local app.Fixes #18307.
BREAKING CHANGE:
WebSocketLambdaAuthorizerProps.identitySourcedefault changes from['$request.header.Authorization']to['route.request.header.Authorization'].By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license