Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Your message was too long by 408 tokens - please shorten it and try again.

 For reference, here's your message at the allowed limit:
&gt; I have a prefect.yaml file that looks like this:
```# Generic metadata about this project
name: amy-ml-server
prefect-version: 2.19.1

# build section allows you to manage and build docker images
build:
- prefect_docker.deployments.steps.build_docker_image:
    id: build_image
    requires: prefect-docker&gt;=0.3.1
    image_name: europe-west2-docker.pkg.dev/amygdadss/prefect-repo/hal-data-pipeline
    tag: v2.1
    dockerfile: ./Dockerfile
    platform: linux/amd64

# push section allows you to manage if and how this project is uploaded to remote locations
push:
- prefect_docker.deployments.steps.push_docker_image:
    requires: prefect-docker&gt;=0.3.1
    image_name: '{{ build_image.image_name }}'
    tag: '{{ build_image.tag }}'

# pull section allows you to provide instructions for cloning this project in remote locations
pull:
- prefect.deployments.steps.set_working_directory:
    directory: /opt/prefect/amy-ml-server

# the deployments section allows you to provide configuration for deploying flows
deployments:
- name: fdr-hal-pipeline-deploy
  version:
  tags: []
  description:
  entrypoint: flows/fdr_flow.py:process_fdr_data
  parameters:
    new