CloudWatch Newline Fix #473
Open
Conversation
This file contains hidden or 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
Signed-off-by: Vitalij Berdinskih <vitalij_r2@outlook.com>
Signed-off-by: Vitalij Berdinskih <vitalij_r2@outlook.com>
Member
|
@vitalijr2 Thank you for this PR. As mentioned earlier, I am unfamiliar with CloudWatch. Thus, I suggest that you publish this version of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As I wrote in #472 there is the specific AWS CloudWatch issue related to using the linefeed character
\nas a separator.And the quick fix exists: replace
\nwith\r.I have added a new configuration key cloudwatchNewlineFix: when it is
trueall linefeed characters are replaced with carriage return ones.I prefer the name cloudwatchNewlineFix instead of replaceNewlineWithCarriageReturn as it is a specific feature and should not be used on any other platform.