Hi folks -- has anyone ever had the need to download the original workflow definition code inside

script_mode.tar.gz

(for instance, to be able to iterate on a copy locally)? This seems like something that could / should be added to flytekit?

@gorgeous-waitress-5026, can you say more? How should that look like?

pyflyte run remote-workflow

allows us to run workflows registered on the server. But rather than running it, maybe we want to: • create a new version with a different name / parameters • register it in a different project • etc For the sake of argument, assume it's not easy to get access to the original code...maybe it: • lives in a git repo you can't access OR • you've lost the original code OR • this is a special template project (and you don't want to use cookiecutter for some reason) My understanding here may be naive on all that would need to happen to get all the code (i.e. if there are sub-workflows involved), but I would think something like

pyflyte clone [workflow] /local/path

or something like that could copy everything down and extract to a local working directory for modification

@gorgeous-waitress-5026, this is an interesting idea. We should probably discuss it a bit more before committing one way or the other. The

script_mode.tar.gz

file is specific to fast registration (so no mention of dependencies, for example). I feel like there's something to

pyflyte clone

but I don't think we should make it work just for fast registration. Are you saying it's a common use case in your Flyte deployment that users need this kind of functionality?

Thanks @high-accountant-32689 for taking a look at the idea. We've had the request come up a few times -- since Flyte is the source of truth for the workflow code, there's a desire to not just be able to restore the code to a local working directory like this, but also inspect it in a browser, etc.