Hello! 👋 We are standardizing our forecasting project layout to meet enterprise standards. We want to separate our orchestration flows from our core business/feature engineering logic. We know Metaflow's remote packaging mechanism natively targets files relative to the flow script's location. If train_flow.py is nested in flows/, running argo create leaves the src/ directory behind, causing a ModuleNotFoundError on the cluster. My Questions: What is the currently recommended pattern to handle this layout? Is creating a symbolic link still the standard workaround for this, or is keeping the flow files strictly at the project root folder considered the cleanest path of least resistance? Are there newer alternative approaches (like specific flags or native configurations) to cleanly include sibling/parent directories during cluster packaging?

We have a new feature for this but looks like it hasn't been open sourced. Let me see what it would take to get it out

Hello, I am looking for some guidance around this as well. Any idea from anyone on if the internal feature will be open sourced? thankyou

github.com/Netflix/metaflow/pull/3351 We have this internally and I just got the PR out. We will merge and release it. It should resolve your isse.

Thank you @rhythmic-controller-77489 tried it out and it does solve the problem I was looking at. It doesn't seem to be in the latest available release though and I worked around that by installing from

master

Any release cadence that I can watch out for? I didn't see anything in the github repo (may have missed it).

Making a release today