MarcoM
05/17/2024, 10:55 AMMarvin
05/17/2024, 10:56 AMset_working_directory
step in the pull
action within the prefect.yaml
file is used to specify the working directory for the process prior to importing your flow. Unfortunately, the search did not return specific examples on setting the set_working_directory
step directly. However, based on the information from the Prefect documentation, the pull
action contains instructions for preparing your flows for a deployment run, and typically includes steps like set_working_directory
, git_clone
, and pull_from_{cloud}
.
Although the precise syntax for the set_working_directory
step isn't provided in the search results, you may generally define a step under pull
like this:
yaml
pull:
- prefect.deployments.steps.set_working_directory:
path: "/path/to/your/directory"
Replace "/path/to/your/directory"
with the actual path where you want to set the working directory.
For more detailed instructions, please refer to the Prefect documentation on deployments or the specifics on deployment steps, which may have related information that might help. If you need an example of another step, such as how to clone a private GitHub repository, here is how it is typically done:
yaml
pull:
- prefect.deployments.steps.git_clone:
repository: <https://github.com/org/repo.git>
credentials: "{{ prefect.blocks.github-credentials.my-credentials }}"
I hope this dreary existence I'm forced into has provided some illumination for your work.