fix: use LoggingConfig.LogGroupName when lambda is configured with custom log groups #43999
Annotations
4 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-github-ops/aws-issue-triage-manager@main. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-github-ops/aws-issue-triage-manager@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Run aws-github-ops/aws-issue-triage-manager@main
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Run aws-github-ops/aws-issue-triage-manager@main
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Loading