logging: Add possibility to log into file #2008
Merged
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
kosstennbl
requested review from
denverwilliams,
wvwatson and
agentpoyo
as code owners
kosstennbl
force-pushed
the
log-path-addition
branch
from
b5e58ab to
76a7632
Compare
taylor
reviewed
Apr 30, 2024
Add processing of environment variables LOGPATH and LOG_PATH If either one exists - logger will log into the file on that path instead of STDOUT. refs: cnti-testcatalog#2000 Signed-off-by: Konstantin Yarovoy <[email protected]>
kosstennbl
force-pushed
the
log-path-addition
branch
from
76a7632 to
622d7d7
Compare
HashNuke
approved these changes
May 7, 2024
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.
Description
Add processing of environment variables LOGPATH and LOG_PATH If either one exists - logger will log into the file on that path instead of STDOUT.
Issues:
Refs: #2000
How has this been tested:
Manual testing of the functionality.
Running new spec.
Types of changes:
New non-breaking feature
Checklist:
Documentation
No documentation update is needed.