You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a working_dir parameter to PipelineDecorator.pipeline and PipelineDecorator.component to be able to set the execution working_dir.
Motivation
Currently when defining a pipeline using PipelineDecorator.component, it's only possible to set the repo for the script execution, but not the working_dir. Therefore it defaults to ., and if all the code is inside a subfolder, when running the pipeline remotely the script it's not able to find any local modules.
Proposal Summary
Add a
working_dir
parameter toPipelineDecorator.pipeline
andPipelineDecorator.component
to be able to set the execution working_dir.Motivation
Currently when defining a pipeline using
PipelineDecorator.component
, it's only possible to set therepo
for the script execution, but not theworking_dir
. Therefore it defaults to.
, and if all the code is inside a subfolder, when running the pipeline remotely the script it's not able to find any local modules.Related Discussion
Original slack thread.
The text was updated successfully, but these errors were encountered: