DevOps

1685 readers

3 users here now

DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.

Rules:

Posts must be relevant to DevOps
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

Ategon

RandomDevOpsDude

What's your approach with Ansible verbosity? (lemmy.org.il)

submitted 1 year ago by [email protected] to c/devops

4 comments fedilink hide all child comments

I recently stumbled upon a problem: I wanted the stdout of a command task to be printed after execution, so I toggled the global -v flag. However, the service module is apparently verbose as shit and printed like a 100 lines and uhh.... that's a costly tradeoff O_o

Seems like a PR for a task-level verbosity keyword has been proposed, yet rejected.

I'm aware it's possible to just register the stdout of the command and print it in a following debug task, but I wonder if there's a prettier solution.

How would you go about this? Ever encountered such a feeling?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 1 year ago (1 children)

The PR wasn't rejected, looks like it was abandoned by the author and otherwise no one seems to care enough about the parent issue.

Anyway, it looks like you pretty much answered your own question.
In general you probably shouldn't care about the output of the commands unless you're debugging some specific issue, in which case "tradeoff" of Ansible actually being verbose is a plus. ;)

[–] [email protected] 1 points 1 year ago

Oh thanks for the heads up, I should've read it more carefully :P