-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Upload Pipeline Version If already exists #3901
Comments
I think it's already supported. Do you mean only-upload/insert versions if there is already a pipeline there? Please update the KFP version for a retry. |
No, I mean. I shouldn't need to get pipeline ID before uploading a version. If Pipeline Exists > Get Pipeline ID > Upload Pipeline Version |
Just a little update, I have update versions, but there's no change of sort that I was looking for.
|
Thank you @talhairfanbentley for raising this issue, I was also looking for the same feature. It should ask the |
I will work on a PR for this. |
…ubeflow#3901 (kubeflow#4087) * Update _client.py * Allow for passing name instead of only pipeline_id * fixed old rebase issue * protobuf fix * raise error and remove f-string * moved file * updated python proto packages versions * Update sdk/python/kfp/_client.py * restructured and added to build * changes structure of import * Updated the files * further updates of client and filter.proto * alternative * clean up * clean up * remove helperfiles * futher clean up * clean up or eaither name or id * update doc strings * remove page_size * Update sdk/python/kfp/_client.py Co-authored-by: Jiaxiao Zheng <jxzheng@google.com> * Update sdk/python/kfp/cli/pipeline.py Co-authored-by: Jiaxiao Zheng <jxzheng@google.com> * updated to classical string formattin Co-authored-by: Jiaxiao Zheng <jxzheng@google.com>
It's not a bug or issue.
In case it doesn't exists, then it's a suggestion
Is there any way I can upload pipeline to kubeflow via sdk, and it just uploads a version if the main pipeline already exists.
Versions:
The text was updated successfully, but these errors were encountered: