Files
zuul/releasenotes/notes/dont-cross-the-streams-d2263c67bd863dff.yaml
Simon Westphahl 3b011296e6 Keep task stdout/stderr separate in result object
Combining stdout/stderr in the result can lead to problems when e.g.
the stdout of a task is used as an input for another task.

This is also different from the normal Ansible behavior and can be
surprising and hard to debug for users.

The new behavior is configurable and off by default to retain backward
compatibility.

Change-Id: Icaced970650913f9632a8db75a5970a38d3a6bc4
Co-Authored-By: James E. Blair <jim@acmegating.com>
2023-08-17 16:22:41 -07:00

18 lines
672 B
YAML

---
features:
- |
A new job attribute, `ansible-split-streams` has been added to
instruct Zuul to keep stdout and stderr separate when running
Ansible command tasks.
deprecations:
- |
Zuul is changing the behavior of its customized Ansible command
module to match the standard Ansible behavior.
The previous behavior and current default is to combine stdout and
stderr streams. In a later Zuul release, the
`ansible-split-streams` default value will change from `false` to
`true` in order to match the standard Ansible behavior and keep
the streams separate. A further Zuul release will remove the
option altogether.