-
Notifications
You must be signed in to change notification settings - Fork 4
fix: Use the new versions api to patch pipeline for overwrite #283
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
Conversation
Instead of the older put `<pipeline>/yaml` endpoint
|
Thanks a lot @bglearning Looks good already, let's fix the failing tests, and it's good to go! |
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
|
@tstadel Updated the tests accordingly. Note: expected but tried out and the indexing update works fine ☑️ |
tstadel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
* Use the new versions api to patch pipeline Instead of the older put `<pipeline>/yaml` endpoint * Update unit tests to align with the PipelineService overwrite update * Fix mypy issues in test_integration_pipeline_client.py
|
@bglearning pr looks good, integration tests are failing here: https://github.com/deepset-ai/deepset-cloud-sdk/actions/runs/19437916146/job/55613612329#step:3:491 |
|
added the integration tests tag to run the tests in the PR |
|
@ArzelaAscoIi Updated it. I think can go back to the merge queue. |
|
merging it! Thank you! |
Instead of the older put
<pipeline>/yamlendpoint we switch to the<pipeline>/versions/<version-id>endpoint.Related Issues
Proposed Changes?
There is a new versions endpoint on the platform. So updating a pipeline involves patch request to that endpoint instead.
How did you test it?
Manual end-to-end.
And update to the unit tests.
Checklist