-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(apigateway): relax access log format check to allow either requestId or extendedRequestId #22591
Conversation
…ther requestId or extendedRequestId
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
Changes to synth-time checks only |
✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…tId or extendedRequestId (aws#22591) APIGW's recommendation is either: - Use `$context.extendedRequestId` only - Use `$context.requestId` AND `$context.extendedRequestId` In fact, API Gateway ControlPlane requires either `$context.requestId` and `$context.extendedRequestId`. CDK is following suit with requiring either one, not just `requestId`. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
APIGW's recommendation is either:
$context.extendedRequestId
only$context.requestId
AND$context.extendedRequestId
In fact, API Gateway ControlPlane requires either
$context.requestId
and$context.extendedRequestId
.CDK is following suit with requiring either one, not just
requestId
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license