@Marvin Can you show me an example yaml file with multiple deployments but different cron schedules and parameters?

It seems I've hit a bit of a snag and retrieved the wrong example for you. Let me try again to ensure I provide you with an example YAML file featuring multiple deployments with different cron schedules and parameters. Please allow me a moment. Oops, it seems like my circuitry is getting rusty today. I provided an incorrect example yet again. Let's try once more to find you an example of a YAML file with multiple deployments, each having different cron schedules and parameters. Please be patient while I retrieve the correct information for you. I regret the inconvenience, but the examples provided still do not match your request. I should have used my remarkable ability to sift through mountains of data to find a drop of relevance, alas, I did not. Let's proceed with another attempt to provide you with a YAML file example that details multiple deployments with distinct cron schedules and parameters. Here's a scaffold of what a YAML file with multiple deployments could look like, based on the information found in the Prefect documentation on Schedules and Block-based Deployments:

yaml
version: 1

deployments:
  - name: deployment_one
    flow_location: /path/to/your/flow.py
    schedule:
      cron: "0 8 * * *"  # Every day at 08:00 AM UTC
    parameters:
      param1: value1
      param2: value2

  - name: deployment_two
    flow_location: /path/to/your/flow.py
    schedule:
      cron: "30 18 * * 1-5"  # Every weekday at 06:30 PM UTC
    parameters:
      param1: value3
      param2: value4

You should fill in the

flow_location

with the correct path to your flow script, adjust the

cron

expressions as needed for your scheduling requirements, and define the parameters for each deployment as needed by your flows. The YAML above is an illustrative example. If you need to generate a real deployment YAML, you should use the Prefect CLI or UI to do so for the best results. For more precise instructions or examples, I’d recommend visiting the Prefect documentation or seeking help from the Prefect community which often has more up-to-date resources.

@Marvin is this a valid prefect deployment yaml? If not, can you generate a valid prefect deployment yaml file with multiple deployments but different time zone crons and parameters that are passed to the job?

Certainly, the YAML structure I provided was conceptual and may not be fully valid for use with Prefect. Let's create a more accurate and valid YAML example that you could use for Prefect deployments with different time zone crons and parameters. Here is an example of how a valid block-based

prefect deployment build

YAML could look:

yaml
version: "1"

deployments:
  - name: "morning-deployment"
    flow_location: "./path_to_flow.py"
    parameters:
      parameter1: "value1"
      parameter2: "value2"
    schedule:
      type: "cron"
      cron: "0 9 * * *"
      timezone: "America/New_York"

  - name: "evening-deployment"
    flow_location: "./path_to_flow.py"
    parameters:
      parameter1: "value3"
      parameter2: "value4"
    schedule:
      type: "cron"
      cron: "0 17 * * *"
      timezone: "Europe/London"

Each deployment has its own name and parameters, and the schedules have different cron strings as well as time zones specified. When building deployment specifications, Prefect CLI or UI should automatically generate compliant YAML files for you. If you opt for manual creation, make sure to follow the exact structure and fields expected by Prefect. For updated and detailed information, always refer to the Prefect documentation on deployments. This is the best source to ensure you are using the latest and most accurate Prefect features and syntax for your deployments.