Skip to content

feat: Configure log levels #248

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

jvanbrunschot
Copy link

@jvanbrunschot jvanbrunschot commented Feb 24, 2025

Description

Configure log levels, defaults to WARN. This way LOG_EVENTS is useless.

Motivation and Context

I was required to have the incoming event but was unable to obtain it without modifying the source code. Allowing us to set the log levels would also allow logging the incoming event

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@jvanbrunschot jvanbrunschot changed the title configure log levels feat: configure log levels Feb 24, 2025
@jvanbrunschot jvanbrunschot changed the title feat: configure log levels feat: Configure log levels Feb 24, 2025
Copy link

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

@github-actions github-actions bot added the stale label Mar 27, 2025
@@ -168,6 +168,12 @@ variable "log_events" {
default = false
}

variable "log_level" {
Copy link
Member

Choose a reason for hiding this comment

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

this variable doesn't appear to be connected to the function as described - if a user changes this to INFO, how does that get propagated?

@github-actions github-actions bot removed the stale label Mar 30, 2025
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 May 22, 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