-
-
Notifications
You must be signed in to change notification settings - Fork 740
fix: Use local log_group throughout, fixing log configuration with Lambda@Edge.
#666
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
Conversation
log_group throughout, fixing log configuration with Lambda@Edge. (削除ここまで)log_group throughout, fixing log configuration with Lambda@Edge. (追記ここまで)
This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days
This PR was automatically closed because of stale in 10 days
Cool, another PR closed out of hand because these repositories are mostly unmonitored. 👍
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Fixes #650 and #665.
Description
Motivation and Context
This allows module implementations using
lambda_at_edge = trueto actually log to Cloudwatch.Breaking Changes
This will cause changes for users using
lambda_at_edge = true, but is is a fixing change.How Has This Been Tested?
pre-commit run -aon my pull request