[Core feature] Automate generation of flyte-ready python projects

[eapolinario]

Motivation: Why do you think this is important?

The very first thing we ask users to do in our Getting started docs is to clone a repo and start making edits to the files in the local copy of that repo. This is less than ideal, instead we should streamline the initial experience and provide an automated way to generate the boilerplate code necessary to run flyte workflows, locally or otherwise.

Goal: What should the final outcome look like, ideally?

The idea of this feature is to provide a command that will be used to generate the boilerplate structure for flyte-ready projects with inputs provided by the user. This could command can be extended to cover a variety of scaffolding for projects, including examples that use GPUs or specific libraries (e.g. a pytorch-enabled project).

Describe alternatives you've considered

https://pypi.python.org/pypi/PasteScript/ - too complicated for our use case
https://pypi.org/project/Voodoo/ - the featureset seems adequate for this feature, but the project appears to be abandoned
https://github.com/copier-org/copier - API is similar to cookiecutter

Propose: Link/Inline OR Additional context

Implement a new pyflyte command that under the covers uses several cookiecutter templates.

The command will be called pyflyte init and initially it'll contain only one sub-command called example, which will correspond to the code used in our getting started docs.

As stated in the goal, the idea is to expand the init command to expose a variety of projects.

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes