Git/GitHub would be nice to clone whole repo @Kevin Kho @Michael Duncan @Benjamin R. Everett We have a bunch of core logic in it's own package that we are building into a core base image to run our specific flows in using the ECS agent. Our specific flows have a fair amount of logic in a couple of modules. We see in the code that both Git and GitHub storage classes only wind up with the flow.py file getting loaded into the image at runtime. Granted they get there by two different. Git clones the repo, extracts the flow.py and then deletes the repo. GitHub downloads just the flow.py file. It seems like it wouldn't be all that difficult to modify the Git storage class to not delete the repo after it extracts the flow.py file and have the root of the modules on PYTHONPATH in the base image. Then when the flow is executed it would be able to find the modules and everything would be Prefect. While we are all noodling on this - is there anything obvious that keeps us from: 1. Creating a new GitRepo storage class that keeps the repo around 2. Adding it to the core package and building it into the core image 3. Adding where that repo's root will be to PYTHONPATH 4. running with the specific models loaded from Git.

Hi @Nathan Atkins - please refrain from tagging individual Prefect members in your posts - we do our best to respond to every message.

Sounds good. Can you include Michael Duncan and Benjamin Everett as well.

Sure thing, I don't know your github handles, would you mind posting them here or DMing them to me?