-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow more control over verbosity when calling ansible-galaxy #278
Allow more control over verbosity when calling ansible-galaxy #278
Conversation
bde85a2
to
9194b43
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I agree that we need to do something about it, we need to find a way to control verbosity from the consumer of compat library instead of harcoding the behavior.
f109077
to
c30bff0
Compare
I made verbosity configurable and got my ideas from https://github.com/ansible/ansible-lint/blob/7bdb009ec56d7f66cbe6c7c7e237a2032b48c7b5/src/ansiblelint/__main__.py#L231 |
c30bff0
to
b37bd47
Compare
@ssbarnea your thoughts on my proposed changes? |
Hi @ssbarnea, any thoughts on my proposed changes? |
…at INFO level This makes ansible-galaxy display important info, when logging level is increased. This helps debugging ansible-lint. Signed-off-by: Daniel Ziegenberg <[email protected]>
Signed-off-by: Daniel Ziegenberg <[email protected]>
Signed-off-by: Daniel Ziegenberg <[email protected]>
8906b6a
to
e14d45a
Compare
Hi @ssbarnea, any thoughts on my proposed changes? I rebased my branch and solved the merge conflict. |
e14d45a
to
be2f4a6
Compare
This makes ansible-galaxy display important info when the logging level is increased. This helps with debugging ansible-lint.
When using
ansible-lint
with maximum verbosity level (-vv
), it currently only outputs:Outputting the
stdout
will help with debugging the installation of requirements.