Make conda-store server launch uvicorn with log level #940
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.
Fixes # #516
(along with #903)
Description
This change ensures that the log level set by the
CondaStoreServer.log_level
config gets applied to the uvicorn server. The default behaviour remains the same, that is, the log level is set toINFO
by default (this is the default by uvicorn when the log_level is not set).To test this out, try running a conda-store server with the following configs:
See info level logging (currently, the only option)
See critical level logging (pretty much no logs output)
Pull request checklist