#638 [Feature] Task & Workflow interface evolution to allow ease of sharability. Issue created by kumare3 Motivation: Why do you think this is important? Flyte tasks and workflows can be shared across projects. A desirable property is to use the latest version of a task when using a shared platform task. this would allow platform owners to deploy new versions of tasks without needing to re-compile all the workflows and still get newer versions Goal: What should the final outcome look like, ideally? USers can keep using new versions of a task (at registration time) and get the latest copy of the task even when the interface was evolved. This could be done like python functions with default values. Describe alternatives you've considered 2 alternatives: 1. all users lock a version of the task locally. they manually update the version and update the corresponding usage 2. for every new release of shared task, we recompile all the workflows - this may not always be possible, but we can introdce default values at usage point - This is extremely complex to do correctly Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☑︎ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline RFP to be done flyteorg/flyte