Downgrade log level when linking Ansible variables #3646
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
Having these log messages emitted at "INFO" level tends to make the output for sequences with many steps (like test) quite noisy.
sleiner
requested review from
greg-hellings,
apatard,
cidrblock,
priyamsahoo and
shatakshiiii
and removed request for
a team
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.
When using the linking feature for Ansible vars, I noticed that it makes the output for sequences with many steps (like test) quite noisy. See this screenshot for example:
Since the symlinks are explicitly requested in
molecule.yml, I would argue that these messages do not have to be this prominent. As far as I see, they are mainly useful when debugging. So I propose changing the log level toDEBUGhere.