Hey All... qq around the runtime env of a flyte workflow. In Quickly Re-deploy Your Application, there's a note:

--fast flag will take the code from your local machine and provide it for execution without having to build the container and push it. The --force flag allows overriding your previously created package.

How does flyte decide what to push up and how does the updated code get packaged into the container without a rebuild?

Hi, @Edgar Trujillo! Flyte serializes code that’s present on your local machine and uploads the same using a signed URL during fast registration, meaning the code and the image aren’t tightly coupled.