Nate
07/26/2023, 11:24 PMMarvin
07/26/2023, 11:24 PMNate
07/26/2023, 11:24 PMMarvin
07/26/2023, 11:24 PMNate
07/26/2023, 11:24 PMMarvin
07/26/2023, 11:25 PMNate
07/26/2023, 11:30 PMMarvin
07/26/2023, 11:31 PMNate
07/26/2023, 11:31 PMMarvin
07/26/2023, 11:38 PMNate
07/26/2023, 11:39 PMMarvin
07/26/2023, 11:39 PMpull
section is indeed an important part of this configuration file. It contains instructions for preparing your flows for a deployment run. These instructions are executed each time a deployment created within this folder is run via a worker.
There are three main types of steps that typically show up in a pull
section:
1. `set_working_directory`: This step sets the working directory for the process prior to importing your flow.
2. `git_clone`: This step clones the provided repository on the provided branch.
3. `pull_from_{cloud}`: This step pulls the working directory from a Cloud storage location (e.g., S3).
All block and variable references within your pull
step will remain unresolved until runtime and will be pulled each time your deployment is run. This allows you to avoid storing sensitive information insecurely; it also allows you to manage certain types of configuration from the API and UI without having to rebuild your deployment every time.
For more detailed information, you can check out these resources:
1. Prefect Documentation
2. Discourse Post on Deployment custom pull steps
I hope this brings some light to your query. If not, well, such is life.