rabbit_prelaunch_logging: $RABBITMQ_LOGS doesn't override log level if it is set in the configuration file #2911
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.
Here is an example of that use case:
RABBITMQ_LOGS=-
in the environmentThe initial implementation, introduced in #2861, considered that if the output is overriden in the environment (through
$RABBITMQ_LOGS
), any output configuration in the configuration file is ignored.The problem is that the output-specific configuration could also set the log level which is not changed by
$RABBITMQ_LOGS
. This patch fixes that by keeping the log level from the configuration (if it is set obviously) even if the output is overridden in the environment.