allow entrypoint in a prefect.yaml to be a python module instead of a path

[Ben-Epstein]

Describe the current behavior

Currently, entrypoint needs to be a path that is relative to the root of your github directory. At the same time, it needs to be relative to the CWD that you are running prefect deploy from, which leads to: you must always call prefect deploy from the root of your directory

This isn't always the best setup for repos (like multi-project repos), and it's also just a bit more confusing than it needs to be: relative-path routing is hard :D

Describe the proposed behavior

I'm proposing that entrypoint allow absolute module paths in python in addition to file paths, keyed internally in prefect by the presence of . in the value. If I have a repo like so

repo
|_ project
|_ _ Makefile
|_ _ pyproject.toml
|_ _ prefect.yaml
|_ _ flows
|_ _ _ my_flow.py

now, I can simply put
entrypoint: flows.my_flow.main instead of having to think about paths. This way, I can guarantee that what i want to be run is being run, and itll work from anywhere.

This can take inspiration from modal, which offers the same modal deploy src/project/app.py or modal deploy project.app both work, and for production i always use the latter.

Example Use

deployments:
- name: my-flow
  version:
  tags: []
  description: Run my flow at some cadence
  entrypoint: my_app.my_flow.main
  ....

Additional context

No response

[Ben-Epstein]

Hm it seems like this might already be possible and just not documented? https://github.com/PrefectHQ/prefect/blob/main/src/prefect/flows.py#L2040C83-L2041C31