Skip to content

fix: use LoggingConfig.LogGroupName when lambda is configured with custom log groups #117702

fix: use LoggingConfig.LogGroupName when lambda is configured with custom log groups

fix: use LoggingConfig.LogGroupName when lambda is configured with custom log groups #117702

Triggered via pull request March 11, 2024 20:30
@onhateonhate
edited #29449
Status Failure
Total duration 1m 55s
Artifacts

pr-linter.yml

on: pull_request_target
download-if-workflow-run
4s
download-if-workflow-run
Fit to window
Zoom out
Zoom in

Annotations

1 error
validate-pr
The pull request linter fails with the following errors: ❌ Features must contain a change to a README file. ❌ Features must contain a change to a test file. ❌ Features must contain a change to an integration test file and the resulting snapshot. ❌ CLI code has changed. A maintainer must run the code through the testing pipeline (git fetch origin pull/29449/head && git push -f origin FETCH_HEAD:test-main-pipeline), then add the 'pr-linter/cli-integ-tested' label when the pipeline succeeds. ❌ Pull requests from `main` branch of a fork cannot be accepted. Please reopen this contribution from another branch on your fork. For more information, see https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md#step-4-pull-request. <b>PRs must pass status checks before we can provide a meaningful review.</b> If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing `Exemption Request` and/or `Clarification Request`.