Skip to content
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

clean up playbook summary output #82

Closed
ggeldenhuis opened this issue Mar 28, 2012 · 5 comments
Closed

clean up playbook summary output #82

ggeldenhuis opened this issue Mar 28, 2012 · 5 comments

Comments

@ggeldenhuis
Copy link

When running a playbook I get the following:

auth01.example.com : ok= 5 changed= 0 unreachable= 1 failed= 0

I think it would be more readable if it looked like:

auth01.example.com : ok=5 changed=0 unreachable=1 failed=0

or even:
auth01.example.com : ok=5, changed=0, unreachable=1, failed=0

@mpdehaan
Copy link
Contributor

ok, I think you're saying you don't like my width controls on the output that keeps things in neat columns when the results go over 1 digit.

I am not sure I want to change this, because then the word 'failed', 'changed', etc, would not always line up.

I could see maybe printing a header and making it tabular, sure.

@ggeldenhuis
Copy link
Author

The problem is that on my console there is significant space between the equals sign and the number. This means that the number is next the next category so it is confusing to read. Unfortunately the formatting engine in github removes this space so it looks more readable than it really is... I have not used ansible in relation to the use case you mention as motivation for the current formatting, but would agree that it would be a good reason.

@mpdehaan
Copy link
Contributor

I'll consider some sort of table output.

On Thursday, March 29, 2012 at 6:48 AM, gjngeldenhuis wrote:

The problem is that on my console there is significant space between the equals sign and the number. This means that the number is next the next category so it is confusing to read. Unfortunately the formatting engine in github removes this space so it looks more readable than it really is... I have not used ansible in relation to the use case you mention as motivation for the current formatting, but would agree that it would be a good reason.


Reply to this email directly or view it on GitHub:
#82 (comment)

@ghost ghost assigned mpdehaan Apr 12, 2012
@mpdehaan
Copy link
Contributor

here's the start of a decent function via a stackoverflow post:

http://stackoverflow.com/questions/5909873/python-pretty-printing-ascii-tables

we'll do something like that

@mpdehaan
Copy link
Contributor

mpdehaan commented May 7, 2012

not planning on doing this any more seeing I've been using this format for a while and it seems fine to me, patches to do the above are welcome however.

@mpdehaan mpdehaan closed this as completed May 7, 2012
@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants