mirror of
https://github.com/run-llama/llama_deploy.git
synced 2026-08-24 21:01:26 -04:00
[PR #209] [MERGED] Detect nested workflows #318
Reference in New Issue
Block a user
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?
📋 Pull Request Information
Original PR: https://github.com/run-llama/llama_deploy/pull/209
Author: @logan-markewich
Created: 8/29/2024
Status: ✅ Merged
Merged: 8/30/2024
Merged by: @logan-markewich
Base:
v0.1.0← Head:logan/detect_nested_workflows📝 Commits (4)
a0c73f3add network service detection modules3bea9f5Merge branch 'v0.1.0' into logan/detect_nested_workflowsb2b1bfcupdate readme, fix small bugsde5f7e6fix missing queue args in tests📊 Changes
4 files changed (+185 additions, -4 deletions)
View changed files
📝
README.md(+97 -0)📝
llama_agents/deploy/deploy.py(+6 -0)➕
llama_agents/deploy/network_workflow.py(+70 -0)📝
tests/message_queues/test_simple_remote_client.py(+12 -4)📄 Description
This PR adds the ability to detect and deploy nested workflows
It works by highjacking the
ServiceManagerthat is inside each workflow. Before injecting the workflow into a step, it optionally checks if that workflow already exists as a service, and then swaps in a new workflow that just makes calls to the remote workflow.This means users need zero code changes to their existing workflows, they just have to deploy everything, and reap the benefits :)
One concern I had was that the nested workflow always creates (and deletes) a new session. Tbh I wanted to reuse the existing session, but couldn't find a way to insert it. Maybe a future PR :)
Script1 (deploying core services)
Script2 (creating and deploying workflows)
Script3 (using the client)
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.