[feature] split up package to appengine and rest

[mokshasoul]

Feature Area

Requirements:

Currently everyone who wants to use this package is force to use urllib < 2.0.0 which is a version although receiving security patches that doesn't play well with cloud environments (e.g. Cloud Composer).

What feature would you like to see?

Since this is an artificial limit to only support engine my suggestion would be to create a feature package (pipeline-components[app-engine], kfp[app-engine]) to support this one use-case instead of generalising it on all pain ponts

What is the use case or pain point?

We publish packages based on cloud composer requirements and this is essentially blocking dependency resolution.

Is there a workaround currently?

I'm preparing a PR that tries to solve this, but essentially short of forking this project the above approach seems a bit more reasonable

I would also like to understand why the monkeypatching is needed, and if it can be solved in a simpler way

we are also aware that we could run this in a PythonVirtualEnvironmentOperator but ideally we want to abstract this away to deferable operators in our own package

---

Love this idea? Give it a 👍.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.