Configure OmniAuth to send log to Rails logger #5004
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
Before this change log generated by OmniAuth was sent to the STDOUT. Now developers will find those gems log within the `app/log` directory as expected.
taitus
approved these changes
Oct 7, 2022
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.
References
Before this change log generated by OmniAuth integration was sent to the STDOUT. Now developers will find the log within the
log/{environment}.logdirectory as expected.https://github.com/omniauth/omniauth#logging
Objectives
Send the Omniauth log to the Rails application logger so developers can easily find the OmniAuth output when debugging.
Notes
We did some tests in the CONSUL testing server and seems to work fine.