Re: [PATCH v4 0/2] Lucid: A custom Ansible stdout callback for kdevops

From: Daniel Gomez <[email protected]>


On Tue, 02 Dec 2025 00:11:15 +0100, Daniel Gomez wrote:
> The Ansible stdout callback ecosystem is quite wide, supporting multiple
> output formats and options. However, after testing a variety of them
> with kdevops workflows, none fit well for our use cases. Most existing
> callbacks provide verbose output that makes it difficult for users to
> understand what's actually happening during playbook executions.
> 
> kdevops relies on Ansible's idempotency principle [1], meaning playbooks
> are designed to reach the desired state regardless of the current state.
> Users shouldn't need to worry about which tasks are running or being
> skipped, the output should simply guide them to the expected result.
> With this principle in mind and inspired by other projects [2] like
> bitbake (from OpenEmbedded/Yocto), we can focus the default output
> on what actually matters: the currently running task, a short list of
> recent tasks, and elapsed time for the current operation.
> 
> [...]

Applied.

[1/2] ansible: use native verbosity config instead of custom AV variable
      commit: 0023c18b915ad719d517e3a42385829ef8892a01
[2/2] ansible: add lucid callback plugin for clean output
      commit: d55d3dcc3462c6071f98800cda7de732f38d8161

Best regards,
-- 
Daniel Gomez <[email protected]>