-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Python functions defined in a pipeline to be run as entrypoint for operations. #979
Comments
JFYI, Python supports putting everything in a function.
Does that solve your problem? BTW, you can probably put the
JFYI, you can use |
Awesome, I had no idea that |
Interesting. Did you get the term "lightweight components" from the documentation or did you just call the feature like that by yourself? The Lightweight python components are shown in this sample notebook which is referenced in the (scarce) documentation. |
Note that we also have a component decorator(
|
Looks like this is resolved. Please reopen if this is not the case. |
* Update the testing branches for kubeflow and manifests Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com> * review: Use a better regex Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
* add generic URI for Storage (kubeflow#826) * handle query parameters * add http as available storage type * update the README * cleanup README * add unit tests * use urlparse to get file name * fail loudly when no filename in uri * inclue http(s) in SupportedStorageURIPrefixList * use regex to check http(s) uri in storage * fix storageURI validation * go fmt * draft for zip & tar archives * fix imports * update tests * support for gzip * draft version of URI examples * newline changes * unit test for http(s) storageUri validation * use mimetypes.guess_type to derive MIME type from url * fix Content-Type validations in storage initializer * update sample README for new ingress access instructions
…ackage pull (kubeflow#979) * update sdk dependency and releases * update sdk dependency and releases
It would be great if lightweight components could be created in a pipeline
.py
file from functions defined inside that pipeline file. I am envisioning something like this:For many tasks it would reduce the number of containers to build and maintain while speeding up the iteration loop. Currently there's support for a dockerless workflow in notebooks. Since our organization is trying to move code out of notebooks for production work, I would love to see it supported in other ways. I don't see this replacing large components, but the ability to author a component that does a short, simple thing seems really powerful.
The text was updated successfully, but these errors were encountered: