@Marvin this is my pull step:

- prefect.deployments.steps.run_shell_script:
    id: change-dir
    script: cd k8-gpu
    stream_output: false

when I run this deployment why does it give me an error at this step that says: FileNotFoundError: [Errno 2] No such file or directory: 'cd'

Well, it seems like the Prefect documentation doesn't directly address changing directories within a deployment step. However, it's important to note that each step in a Prefect deployment is executed in its own shell, and the

cd

command only changes the directory for the current shell. So, even if the

cd

command was executed successfully, the directory change wouldn't persist to the next step. Instead of using the

cd

command, you might want to consider specifying the full path to the file or directory you're trying to access in your script. This way, you don't need to change the current working directory. If you're trying to run a script located in the

k8-gpu

directory, you could do something like this:

yaml
- prefect.deployments.steps.run_shell_script:
    id: run-script
    script: /full/path/to/k8-gpu/your_script.sh
    stream_output: false

Replace

/full/path/to/k8-gpu/your_script.sh

with the actual full path to your script. Remember, life is like a shell script. You never know what you're gonna get. Especially when you're trying to

cd

into a directory that doesn't exist in the current shell.

In this case, have you considered using our

set_working_directoy

pull step? https://docs.prefect.io/2.10.18/concepts/deployments-ux/#the-pull-action https://docs.prefect.io/2.10.18/api-ref/prefect/deployments/steps/pull/?h=set_working#prefect.deployments.steps.pull.set_working_directory

ahh I was not aware of that! Thank you @Serina!

@Serina thanks I did see that in the source code but didn't see an example of what they key/deployment should look like with that argument

Here’s an example from our recipe, which we could add to the docs: https://github.com/PrefectHQ/prefect/blob/bcb18a82d6f2e726ea63cb4aad8bce4d1029d34c/src/prefect/deployments/recipes/docker/prefect.yaml#L24-L26

what would it be relative to? @Serina, essentially I'm trying to use flows inside a monorepo

You only need

id

field if you plan to use it in a downstream step

so my directory structure would be like: myproject/ myproject/pipeline1/myflow.py myproject/pipeline1/prefect.yaml myproject/pipeline2/myflow.py myproject/pipeline2/prefect.yaml

Relative to where your flow is

relative to the root of the repo that get's cloned in? or relative to where I run the prefect deploy command from

If your

prefect.yaml

is in the same directory as

myflow.py

, why do you want to change the directory?

currently one prefect.yaml at root of repo is the only pattern that is supported

Yeah that would be ideal, I'm trying to find a way to make this work with a mono repo

By mono-repo do you mean multiple prefect.yaml files?

I think @Nate has an example here: GitHub - zzstoatzz/prefect-monorepo

run_shell_script just returns output in a subshell