[PR #419] [MERGED] feat: Reload a running deployment. #452

Closed
opened 2026-02-16 01:17:25 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/419
Author: @masci
Created: 1/2/2025
Status: Merged
Merged: 1/4/2025
Merged by: @masci

Base: mainHead: massi/322


📝 Commits (8)

📊 Changes

15 files changed (+405 additions, -54 deletions)

View changed files

📝 e2e_tests/apiserver/deployments/deployment1.yml (+2 -2)
📝 e2e_tests/apiserver/deployments/deployment2.yml (+2 -2)
e2e_tests/apiserver/deployments/deployment_reload1.yml (+15 -0)
e2e_tests/apiserver/deployments/deployment_reload2.yml (+15 -0)
e2e_tests/apiserver/deployments/src/__init__.py (+6 -0)
e2e_tests/apiserver/deployments/src/workflow_reload.py (+11 -0)
e2e_tests/apiserver/test_reload.py (+26 -0)
📝 llama_deploy/apiserver/deployment.py (+85 -24)
📝 llama_deploy/apiserver/routers/deployments.py (+3 -4)
📝 llama_deploy/cli/deploy.py (+5 -2)
📝 llama_deploy/client/models/apiserver.py (+6 -3)
📝 llama_deploy/services/workflow.py (+8 -4)
📝 tests/apiserver/routers/test_deployments.py (+211 -7)
📝 tests/apiserver/test_deployment.py (+9 -6)
📝 tests/client/models/test_apiserver.py (+1 -0)

📄 Description

Fixes #322

Reload a running deployment by restarting its services. The message queue and the control plane won't be restarted, the thread running the dedicated ioloop for this deployment will stay active.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/llama_deploy/pull/419 **Author:** [@masci](https://github.com/masci) **Created:** 1/2/2025 **Status:** ✅ Merged **Merged:** 1/4/2025 **Merged by:** [@masci](https://github.com/masci) **Base:** `main` ← **Head:** `massi/322` --- ### 📝 Commits (8) - [`17d7599`](https://github.com/run-llama/llama_deploy/commit/17d759950a0532d443c4e7c789edc359fc194469) propagate reload param - [`973b27d`](https://github.com/run-llama/llama_deploy/commit/973b27d5b848f3a0b4ba33dcd31f6dbb6d8cc5c8) add test data - [`0841d48`](https://github.com/run-llama/llama_deploy/commit/0841d48a1f4a5428728a17ea314c7feeb0f5b528) add more test data - [`ce6d54d`](https://github.com/run-llama/llama_deploy/commit/ce6d54d64b446757f3e8fe99342809c09725a4cf) add reload functionality - [`1d59d2f`](https://github.com/run-llama/llama_deploy/commit/1d59d2fb2f73cba5a40241805e0b18edbc057254) fix tests - [`8fa4206`](https://github.com/run-llama/llama_deploy/commit/8fa42061124739358fcd2b555e3e7467ad4a244c) add more tests - [`c443b42`](https://github.com/run-llama/llama_deploy/commit/c443b42cafb8809103e6d032360bb129c513a960) add comments - [`686afbd`](https://github.com/run-llama/llama_deploy/commit/686afbda91a68bae37f84659dcd5c90cdd8934c5) more comments ### 📊 Changes **15 files changed** (+405 additions, -54 deletions) <details> <summary>View changed files</summary> 📝 `e2e_tests/apiserver/deployments/deployment1.yml` (+2 -2) 📝 `e2e_tests/apiserver/deployments/deployment2.yml` (+2 -2) ➕ `e2e_tests/apiserver/deployments/deployment_reload1.yml` (+15 -0) ➕ `e2e_tests/apiserver/deployments/deployment_reload2.yml` (+15 -0) ➕ `e2e_tests/apiserver/deployments/src/__init__.py` (+6 -0) ➕ `e2e_tests/apiserver/deployments/src/workflow_reload.py` (+11 -0) ➕ `e2e_tests/apiserver/test_reload.py` (+26 -0) 📝 `llama_deploy/apiserver/deployment.py` (+85 -24) 📝 `llama_deploy/apiserver/routers/deployments.py` (+3 -4) 📝 `llama_deploy/cli/deploy.py` (+5 -2) 📝 `llama_deploy/client/models/apiserver.py` (+6 -3) 📝 `llama_deploy/services/workflow.py` (+8 -4) 📝 `tests/apiserver/routers/test_deployments.py` (+211 -7) 📝 `tests/apiserver/test_deployment.py` (+9 -6) 📝 `tests/client/models/test_apiserver.py` (+1 -0) </details> ### 📄 Description Fixes #322 Reload a running deployment by restarting its services. The message queue and the control plane won't be restarted, the thread running the dedicated ioloop for this deployment will stay active. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 01:17:25 -05:00
yindo closed this issue 2026-02-16 01:17:25 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_deploy#452