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 255 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:
```name: amy-ml-server
prefect-version: 2.19.1


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:
- 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:
- prefect.deployments.steps.set_working_directory:
    directory: /opt/prefect/amy-ml-server


deployments:
- name: fdr-hal-pipeline-deploy
  version:
  tags: []
  description:
  entrypoint: flows/fdr_flow.py:process_fdr_data
  parameters:
    new_file_list: ["heathrow/log/CTX_FDRS_EVENTS_TSV/2023-01-01_East_Events.tsv"]
  work_pool:
    name: cloud-run-work-pool
    work_queue_name: default
    job_variables:
      image: '{{ build_image.image }}'
  schedules: []

