run-llama/llama_deploy
1
0
Fork 0
mirror of https://github.com/run-llama/llama_deploy.git synced 2026-08-24 21:01:26 -04:00
Code Issues 37 Packages Projects Releases 10 Wiki Activity

[PR #547] [MERGED] refact: move workflow execution within Deployment class #541

New Issue
Closed
opened 2026-02-16 02:15:33 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 02:15:33 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/547
Author: @masci
Created: 6/20/2025
Status: ✅ Merged
Merged: 6/20/2025
Merged by: @masci

Base: main ← Head: massi/refact

📝 Commits (3)

📊 Changes

6 files changed (+593 additions, -143 deletions)

View changed files

📝 llama_deploy/apiserver/deployment.py (+33 -1)
📝 llama_deploy/apiserver/routers/deployments.py (+78 -100)
📝 pyproject.toml (+2 -1)
📝 tests/apiserver/routers/test_deployments.py (+24 -41)
📝 tests/apiserver/test_deployment.py (+233 -0)
📝 uv.lock (+223 -0)

📄 Description

Preparing MCP integration

🔄 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/547 **Author:** [@masci](https://github.com/masci) **Created:** 6/20/2025 **Status:** ✅ Merged **Merged:** 6/20/2025 **Merged by:** [@masci](https://github.com/masci) **Base:** `main` ← **Head:** `massi/refact` --- ### 📝 Commits (3) - [`822aa1c`](https://github.com/run-llama/llama_deploy/commit/822aa1c0be48ad70f75cdb23d925bfe585f535d7) refact: move workflow execution within Deployment class - [`c67cb80`](https://github.com/run-llama/llama_deploy/commit/c67cb8011ccf9fa7f258c61a2b6f89dc6f4392d4) fix e2e - [`58f793e`](https://github.com/run-llama/llama_deploy/commit/58f793e594621f6a6dd83e14767fa4e30aa3d2a7) add unit tests ### 📊 Changes **6 files changed** (+593 additions, -143 deletions) <details> <summary>View changed files</summary> 📝 `llama_deploy/apiserver/deployment.py` (+33 -1) 📝 `llama_deploy/apiserver/routers/deployments.py` (+78 -100) 📝 `pyproject.toml` (+2 -1) 📝 `tests/apiserver/routers/test_deployments.py` (+24 -41) 📝 `tests/apiserver/test_deployment.py` (+233 -0) 📝 `uv.lock` (+223 -0) </details> ### 📄 Description Preparing MCP integration --- <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 02:15:33 -05:00
yindo closed this issue 2026-02-16 02:15:33 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
P1
P2
bug
documentation
documentation
enhancement
example
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
topic:CLI
topic:SDK
topic:SDK
topic:SDK
topic:apiserver
topic:control_plane
topic:message_queues
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_deploy#541
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?