refactor: change sqlalchemy_oso authorization logs from INFO to DEBUG level
#1726
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
kkirsche
changed the title
sqlalchemy_oso authorization logs from INFO to DEBUG level
gj
approved these changes
Nov 18, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 merge request changes the log level of
sqlalchemy_oso's authorization logs fromINFOtoDEBUG. In applications where logging is used,INFOmakes for extremely noisy logs, making it hard to use logging more broadly. As this is primarily about authorization decision making, this seems like it can be changed toDEBUGand stay in line with the intent of this use case.An example log output in an application:
PR checklist: