acoustic-carpenter-78188
03/10/2024, 12:01 PMShellTask
where users are unable to retrieve standard output (stdout) and standard error (stderr) from executed ShellTasks directly. Users would have to write both channels to the disk, reading them back to retrieve the command result, and finally deleting them. All those are unnecessary steps which increase disk accesses and make the task writing heavier.
Goal: What should the final outcome look like, ideally?
Expected Behavior:
Users should have the capability to access the stdout and stderr outputs generated during the execution of a ShellTask.
Describe alternatives you've considered
I've considered implementing a custom ShellTask
class that would be 99% the same code as flytekit.extras.tasks.shell.ShellTask
... Not very satisfying...
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteacoustic-carpenter-78188
03/10/2024, 12:01 PM