Skip to content

fix: powertools specific log level env var to not conflict with the system LOG_LEVEL #306

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
Mar 1, 2021

Conversation

pankajagrawal16
Copy link
Contributor

**Issue #293

Description of changes:

Checklist

Breaking change checklist

**RFC issue #

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@msailes
Copy link
Contributor

msailes commented Mar 1, 2021

How will this effect people who are using the existing env var?

@pankajagrawal16
Copy link
Contributor Author

pankajagrawal16 commented Mar 1, 2021

How will this effect people who are using the existing env var?

It should not effect since it didn't worked anyways and had no effect

Copy link
Contributor

@msailes msailes left a comment

Choose a reason for hiding this comment

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

👍

@pankajagrawal16 pankajagrawal16 merged commit 4505213 into master Mar 1, 2021
@pankajagrawal16 pankajagrawal16 deleted the log-level branch March 1, 2021 13:09
This was referenced Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants