Short answer: it’s almost right. In Prefect 3.x, the only issue here is the env var templating. Use

{{ $REPO_DIR }}

instead of

{{ env.REPO_DIR }}

. What you have (with one fix):

name: hpc-orchestration
prefect-version: 3.4.20

deployments:
- name: local-hpc-training
  entrypoint: flows/hpc_submit_flow.py:hpc_training_flow
  description: "Deployment that submits and monitors an LSF job on HPC"
  work_pool:
    name: staging
  parameters: {}
  pull:
  - prefect.deployments.steps.set_working_directory:
      directory: "{{ $REPO_DIR }}"

Notes: -

deployments[].pull

is valid at the per-deployment level in 3.x. -

prefect.deployments.steps.set_working_directory

is a valid pull step. -

work_pool: { name: staging }

and the

entrypoint

are correctly structured. -

prefect-version

is just metadata; keeping it in sync with your installed version is a good practice. References: - prefect.yaml guide (templating and pull steps) - pull steps source