-
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
[feature] Adding description to pipeline version #6256
Comments
Thank you for explaining the use case clearly! |
@Bobgy any pointers to how to add a field? Seems I can should add it pipelines/backend/api/pipeline.proto Line 324 in cc83e10
|
Backend code: https://github.com/kubeflow/pipelines/tree/master/backend pipelines/backend/api/pipeline.proto Line 324 in 7872bd4
Regenerate code after updating proto, https://github.com/kubeflow/pipelines/tree/master/backend/api#auto-generation-of-go-client-and-swagger-definitions Pipeline server:
Resource manager:
Pipeline store (db layer):
UI pipeline details page: https://github.com/kubeflow/pipelines/blob/master/frontend/src/pages/PipelineDetails.tsx Here are most of related code you need to touch, feel free to ask for help if you have further questions! |
Started backend changes in #6261 . I regenerated most code and seems backend is working (mostly just ran unit tests to ensure data was being written to DB and could be read back). Missing to run some integration tests (need to spend more time to add integration tests). |
Thank you for implementing the backend API change! Welcome continuing the UI integration, but you can always leave that to a different contributor too. |
I'm happy to contribute to UI as well. Using this as a learning opportunity. However if someone else comes w this issue and wants to implement it, let me know! (I will add to my backlog once backend gets merged, but I dont know when I can focus on this) |
…6256 (#6261) * start adding description to version * add description to resource manager * remove description from pipeline default version * update pipeline_store * add some tests to ensure its being passed around * update frontend generated api * run auto formatter * add comment to frontend readme about running npm run format * add missing api converter step
Start frontend changes, found out that I missed an endpoint for backend (the HTTP upload one, as those dont use grpc) |
Will also start a separate PR to update kfp sdk |
There's a report the SDK change caused a regression:
|
I'll be taking a look |
@Bobgy This mismatch is present in the latest released sdk package 1.7.2. Could you build a new patch version with this fixed? |
btw, fixed it #6472 |
…#6393) * add description to upload_pipeline_description http endpoint * add test for pipeline upload server description * add description to new pipeline version * show pipeline version in pipeline detail page * make description optional on UI + show version descriptio or pipeline description * remove unused reference * revert wrong change of ref * updated on should be pipeline version * add more versions to mock-backend * show pipeline and version description at the same time * add tests for UI * show pipeline version always
#6472) * add description optionally * add release notes * add new line * capture if description is not accepted by server * add todo comment * add better description api missing exception
Merged. I believe now the only missing part is for this to be released on the next KFP release |
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. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
Feature Area
/area frontend
/area backend
What feature would you like to see?
While using KFP, we lack a way to add descriptions to the pipeline version. This would be useful for example to track metadata of the version uploaded (like for example what git sha was this version generated from).
What is the use case or pain point?
Easier integration into CD systems for continous compilation and deployment of pipeline versions.
Is there a workaround currently?
Hard to do, you can modify the description of the main pipeline and append new lines for each version, that said it may eventually overload that column and make it hard to read vs just having it on the version itself.
Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.
The text was updated successfully, but these errors were encountered: