Fyi figured out an annoying detail of the paths with deploying via a yaml for ecs push pools. In my yaml, I defined pull from s3 step:

pull:
- prefect_aws.deployments.steps.pull_from_s3:
    requires: prefect-aws>=0.3.0
    bucket: 'bucket-name'
    folder: 'src'

And the flow deployment is:

- name: 'sleepy_${short_env}'  
  flow: flows/sleepy_flow.py
  entrypoint: flows/sleepy_flow.py:sleepy_flow

Now this is great and dandy since I finally got it working, but given the redundancies of

flows/

I was hoping to use the folder option in the pull step to declare flows and then my deployment could be

- name: 'sleepy_${short_env}'  
  flow: sleepy_flow.py
  entrypoint: sleepy_flow.py:sleepy_flow

Which is a lot cleaner imo. The ideal layout of my bucket was flows/flow.py. The problem here is that it appears the file location is checked BOTH at the deploy time AND at run time. The latter makes perfect sense since it's a push pool, but the former appears to fail without a directory before the flow name? I can't quite decipher what the precise underlying issue is given

flow = load_flow_from_entrypoint(deploy_config["entrypoint"])

and

FileNotFoundError: [Errno 2] No such file or directory: 'sleepy_flow.py'

. I guess i'm going with src/ but would love to understand my pitfall here.

feels like an enhancement to me https://github.com/PrefectHQ/prefect/issues/new/choose

I'm happy to submit the enhancement but I'm not sure I've fully figured out the core issue. Despite numerous questions here and to Marvin. I'll check it out.

When I find myself in times of prefect.yaml trouble, @Kevin Grismore speaks to me

I did submit the enhancement