Skip to content
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

add log-level helm param #312

Merged
merged 1 commit into from
Dec 10, 2020
Merged

add log-level helm param #312

merged 1 commit into from
Dec 10, 2020

Conversation

brycahta
Copy link
Contributor

@brycahta brycahta commented Dec 9, 2020

Issue #, if available:

  • N/A: helm param for log level was missing

Description of changes:

  • added param

Testing:

  • added various log levels (debug, info, error) to e2e tests, executed locally, and saw pod logs reflected the configuration

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@brycahta brycahta requested a review from haugenj December 9, 2020 23:20
@@ -76,6 +76,9 @@ taintNode: false
# Log messages in JSON format.
jsonLogging: false

# Sets the log level
logLevel: "info"
Copy link
Contributor

Choose a reason for hiding this comment

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

should we leave this as "" ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My thought is it's easier to figure out the default value this way.

If we leave it as "" , then helm readme would have default value say "" too (even though app will default to 'info') OR we have the helm default value actually say info, but then the value in values.yaml would be "" and not match which is confusing/doesn't align with how we documented other vals.

Copy link
Contributor

@haugenj haugenj left a comment

Choose a reason for hiding this comment

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

👍

@brycahta brycahta merged commit 58d4532 into aws:main Dec 10, 2020
@brycahta brycahta deleted the fixn branch December 10, 2020 18:07
haugenj pushed a commit to haugenj/aws-node-termination-handler that referenced this pull request Dec 14, 2020
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