aloof-gpu-13406
01/06/2023, 6:34 PM{steps.step.log}
just outputs "Step command includes global options that will be ignored...". Nothing else in the steps object has any of the logs I'd expect from my script.
Is there any way to save or bubble stdout that happens within the Garden Exec, or do I need to just save to file from the script in question?
Thanks!quaint-dress-831
01/09/2023, 3:00 PMaloof-gpu-13406
01/10/2023, 10:05 PMworkflows.garden.yaml
kind: Workflow
steps:
- name: hideslogs
script: |
garden exec --interactive=false whereIWantScriptToExectute "runscript.sh"
runscript.sh
(Python script using @click
.echo to stdout)
Whether I define it as a script or a command step, stdout ranges from (1) graph resolution logs then nothing from my actual script to (2) no logs at all.
When I pipe the stdout, same thing.
I could change the script to log to file, but then I'd need to do some file mounting to get that log file out, and it feels like there should be a way to just bubble stdout up through the garden exec
Note: Since my original question, I was able to test - running the garden exec command from the command line seemed to show the logs in stdout that we expected, so the cause of this issue is with the Garden workflow, not the garden exec commandgarden exec --interactive=false whereIWantScriptToExectute logs.log<(runscript.sh)
)quaint-dress-831
01/14/2023, 6:00 AMaloof-gpu-13406
01/14/2023, 6:23 PMancient-diamond-80011
01/17/2023, 2:14 PMaloof-gpu-13406
01/17/2023, 5:05 PMancient-diamond-80011
01/18/2023, 7:27 AMglamorous-caravan-26619
01/18/2023, 2:05 PMaloof-gpu-13406
01/27/2023, 5:30 PM