-
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(appsync): use logretention to always create a log group #28527
Conversation
This ensures that if the log group property of GraphQLApi is referred a log group is created beforehand
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.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
This change creates log group for the graphql api even when logging is not enabled and refers the LogRetention custom resource for the property logGroup of
GraphqlApi
.using
new LogGroup()
can sometimes fail if the log group with same name exists however the custom resource LogRetention will create if not exists.This in turn will avoid the race condition when a subsequent resource that refers GraphqlApi.logGroup is being created in the same stack.
Because the logGroup is now referring to the custom resource's output log ARN and further resources will depend on the custom resource to be created first.
Appsync will not fail if a log group is already present with the api id. It will continue to send logs in it.
Closes #26564
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license