Adding zap-time-encoding argument to the KEDA Operator Deployment #766
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…allow changing of the time format used in logging Signed-off-by: Travis Bickford <tbickford@shutterstock.com>
ahmelsayed
approved these changes
Apr 21, 2020
|
@tbickford thanks a lot! |
Signed-off-by: Travis Bickford <tbickford@shutterstock.com>
|
@zroubalik Thank you - Updated some of the description in the Logging section of the README. Let me know if you would prefer something different. |
zroubalik
approved these changes
Apr 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This argument allows for changing of the timestamp date format in the logging of the KEDA Operator. This corresponds to the PR I have for the KEDA Helm Chart - kedacore/charts#41. I have left the
zap-time-encoding-formatat the default of the Operator SDK -epoch.