I think a solution here could be some functionality in agents to monitor some directory and register flows from it if file is changed. This will solve several problems: flow version will be bumped only when file is changed; no need to write anything yourself; flows registration is streamlined and similar to how airflow scheduler works. you just put flows source code in some directory and dont care.What do you think? I would love to try to implement this myself 😎
Hi Alexander, I am in a similar situation as yourself, and have been exploring ways to deploy prefect in a production environment. Flow registration is definitely a confusing piece for me, too, and I'd be interested to see how it is done. I think this is a shortcoming in the documentation but agree that the prefect code is extremely well written and useful to read.
@Alexander a few of us have actually thrown around the idea of something similar to what you are proposing! It would be really cool to have something where you can point your agent to a directory/repo/bucket and when a flow run is to be deployed it will grab the flow from that location, reregister it if it has changed, then deploy the flow run. It’s pseudo similar to this but not entirely. Would definitely encourage a PR or issue to outline this further!@Billy McMonagle we’re always looking to improve the documentation! I can see how registration might be confusing / lacking in the documentation. I’ve opened an issue here to track it 🙂https://github.com/PrefectHQ/prefect/issues/3513
1 year ago
hey @josh that's awesome, appreciate the attention on this issue!