Skip to content

fix: Modify logging for security inspector issue #249

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

Merged
merged 1 commit into from
Feb 25, 2025

Conversation

jreichhold
Copy link
Contributor

Description

Logging is being flagged by AWS Inspector for log injection

Motivation and Context

Log injection fix

Breaking Changes

No

How Has This Been Tested?

  • [x ] I have tested and validated these changes using one or more of the provided examples/* projects
    Veriified by updating on existing lambda and seeing the lambda issue clear in Inspector
  • [ x] I have executed pre-commit run -a on my pull request

@antonbabenko antonbabenko changed the title modify logging for security inspector issue fix: Modify logging for security inspector issue Feb 25, 2025
Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@antonbabenko antonbabenko merged commit b3cd40f into terraform-aws-modules:master Feb 25, 2025
8 of 9 checks passed
antonbabenko pushed a commit that referenced this pull request Feb 25, 2025
## [6.5.2](v6.5.1...v6.5.2) (2025-02-25)

### Bug Fixes

* Modify logging for security inspector issue ([#249](#249)) ([b3cd40f](b3cd40f))
@antonbabenko
Copy link
Member

This PR is included in version 6.5.2 🎉

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants