I recommend us go with hosting the generated code in a sub module instead so we can have more control over the client. For example, we can add our own extension code for new auth methods etc. That way, we will also be able to manage our own user friendly readme. The generated README is too dense for onboarding purpose.

Here is an example on how k8s manages their generated python client in submodules: https://github.com/kubernetes-client/python. Airflow's go client took the same approach as well.

@houqp yeah, even I thought the same but didn't bother to do that as it was the first code push in this repo. Raised #2 for the same.