The zos_copy and zos_fetch modules handle data transfer between z/OS and non z/OS platforms, which leaves room for unexpected behavior in the event that stdout/stderr data is backlasescaped in the proposed solution for the UTF-8 warning.
In this task, I wrote playbooks around both modules to analyze any changes in functionality for these two modules, and paid particular attention to copying and fetching data in binary mode.
I uncovered no gaps in functionality over the course of my investigation. I think this is primarily because the data is handled as a separate stream (of bytes where applicable) so the stdout/stderr streams are not involved and hence the non-utf8 chars warning is not triggered.
This item is a sub-task for:
987
The zos_copy and zos_fetch modules handle data transfer between z/OS and non z/OS platforms, which leaves room for unexpected behavior in the event that stdout/stderr data is backlasescaped in the proposed solution for the UTF-8 warning.
In this task, I wrote playbooks around both modules to analyze any changes in functionality for these two modules, and paid particular attention to copying and fetching data in binary mode.
I uncovered no gaps in functionality over the course of my investigation. I think this is primarily because the data is handled as a separate stream (of bytes where applicable) so the stdout/stderr streams are not involved and hence the non-utf8 chars warning is not triggered.
See attached playbooks for recreate
zoscopy.txt
zosfetch.yml.txt