feature: Add adapters/svc1zap for code that accepts *zap.Logger #198
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
tabboud
requested changes
Apr 22, 2022
Co-authored-by: Tony Abboud <tdabboud@hotmail.com>
|
@tabboud done! |
tabboud
approved these changes
Apr 22, 2022
|
Released 1.20.0 |
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.
Similar in inspiration to long-stalled #114. In some products that use witchcraft logging, we depend on packages that use zap. This adapter lets us create a zap logger which delegates to svc1log for emitting SLS-valid payloads.
Examples of open-source libraries which accept zap outputs but we want logs emitted as service.1:
==COMMIT_MSG==
Add
adapters/svc1zapfor code that accepts*zap.Logger==COMMIT_MSG==
This change is