Skip to content

Conversation

@bglearning
Copy link
Contributor

@bglearning bglearning commented Nov 14, 2025

Instead of the older put <pipeline>/yaml endpoint 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

  • I have updated the referenced issue with new insights and changes
  • If this is a code change, I have added unit tests
  • I've used the conventional commit specification for my PR title
  • I updated the docstrings
  • If this is a code change, I added meaningful logs and prepared Datadog visualizations and alerts

Instead of the older put `<pipeline>/yaml` endpoint
@tstadel
Copy link
Member

tstadel commented Nov 14, 2025

Thanks a lot @bglearning Looks good already, let's fix the failing tests, and it's good to go!

@github-actions
Copy link

Coverage report

Click to see where and how coverage changed

FileStatementsMissingCoverageCoverage
(new stmts)
Lines missing
  deepset_cloud_sdk/_service
  pipeline_service.py
Project Total  

This report was generated by python-coverage-comment-action

@bglearning bglearning marked this pull request as ready for review November 17, 2025 14:18
@bglearning bglearning requested a review from a team as a code owner November 17, 2025 14:18
@bglearning
Copy link
Contributor Author

@tstadel Updated the tests accordingly.

Note: expected but tried out and the indexing update works fine ☑️

Copy link
Member

@tstadel tstadel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@tstadel tstadel added this pull request to the merge queue Nov 17, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 17, 2025
@tstadel tstadel added this pull request to the merge queue Nov 17, 2025
github-merge-queue bot pushed a commit that referenced this pull request Nov 17, 2025
* 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
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 17, 2025
@ArzelaAscoIi
Copy link
Member

@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

@ArzelaAscoIi
Copy link
Member

ArzelaAscoIi commented Nov 18, 2025

added the integration tests tag to run the tests in the PR

@bglearning
Copy link
Contributor Author

@ArzelaAscoIi Updated it. I think can go back to the merge queue.

@ArzelaAscoIi ArzelaAscoIi added this pull request to the merge queue Nov 18, 2025
@ArzelaAscoIi
Copy link
Member

merging it! Thank you!

Merged via the queue into main with commit 4c33494 Nov 18, 2025
9 checks passed
@ArzelaAscoIi ArzelaAscoIi deleted the fix-pipeline-overwrite branch November 18, 2025 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pipeline overwrite doesn't work with the new platform pipeline versions functionality

4 participants