#4936 [Core feature] improve flyte remote registration DX Issue created by samhita-alla ### Motivation: Why do you think this is important? Observed quite a couple of times where flyteremote's

register_task

and

register_workflow

lead to some sort of no module found errors: https://discuss.flyte.org/t/13551857/hi-i-am-testing-remote-access-and-get-some-basic-questions-w#06ee2389-8d32-4118-8b20-83809484e62d and https://discuss.flyte.org/t/16600910/i-built-a-custom-image-and-pushed-it-to-the-demo-docker-regi. While

register_script

works fine, it requires specifying the

source_root

and

module_name

, which can be confusing. ### Goal: What should the final outcome look like, ideally? Registration with Flyte remote should be seamless. It shouldn't lead to any sort of 'no module found' errors. ### Describe alternatives you've considered Use

register_script

instead of

register_task

and

register_workflow

. ### Propose: Link/Inline OR Additional context Kevin's suggestion: we could add a flag (fast) to

register_task

. thus, it can upload the workflow code by flytekit itself. ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte