[PR #266] [MERGED] feat: Allow configuration of the message queue in the deployment config file #365

New Issue

2026-02-16T01:17:03-05:00

yindo commented

2026-02-16 01:17:03 -05:00

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/266
Author: @masci
Created: 9/23/2024
Status: ✅ Merged
Merged: 9/23/2024
Merged by: @masci

Base: main ← Head: massi/message-queue-config

📝 Commits (6)

ca29521 first
6bd08f1 try
2d431ed increase test coverage
8bc4481 Merge branch 'main' into massi/message-queue-config
14b2a54 fix conflicts
18a54a4 add union discriminant to the existing config models

📊 Changes

11 files changed (+166 additions, -33 deletions)

View changed files

📝 llama_deploy/apiserver/config_parser.py (+22 -2)
📝 llama_deploy/apiserver/deployment.py (+48 -10)
📝 llama_deploy/message_queues/apache_kafka.py (+7 -8)
📝 llama_deploy/message_queues/aws.py (+3 -1)
📝 llama_deploy/message_queues/rabbitmq.py (+5 -2)
📝 llama_deploy/message_queues/redis.py (+6 -3)
📝 llama_deploy/message_queues/simple.py (+5 -4)
📝 tests/apiserver/conftest.py (+14 -0)
📝 tests/apiserver/data/example.yaml (+5 -0)
📝 tests/apiserver/test_config_parser.py (+3 -0)
📝 tests/apiserver/test_deployment.py (+48 -3)

📄 Description

Add a section in the deployment config file to define the message queue to use.

Notes:

a string literal field type was added to the existing config models so that we can use it to tell Pydantic what's the right model to use when loading message-queue from the config

The format will be:

message-queue:
  type: simple
  # this section depends on the type of the message queue and will be validated accordingly
  host: "127.0.0.1"
  port: 8001

_{🔄 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/266 **Author:** [@masci](https://github.com/masci) **Created:** 9/23/2024 **Status:** ✅ Merged **Merged:** 9/23/2024 **Merged by:** [@masci](https://github.com/masci) **Base:** `main` ← **Head:** `massi/message-queue-config` --- ### 📝 Commits (6) - [`ca29521`](https://github.com/run-llama/llama_deploy/commit/ca2952185f6e860866af498ddb3575412e79c93c) first - [`6bd08f1`](https://github.com/run-llama/llama_deploy/commit/6bd08f195e662add76168d27291c6af8e5b74388) try - [`2d431ed`](https://github.com/run-llama/llama_deploy/commit/2d431edb005bfaf30f005ae34fbb805fecb6bdf3) increase test coverage - [`8bc4481`](https://github.com/run-llama/llama_deploy/commit/8bc44813068d474bfee42a99addf30c4334255e2) Merge branch 'main' into massi/message-queue-config - [`14b2a54`](https://github.com/run-llama/llama_deploy/commit/14b2a5460f2cc40cf3494944fafff3cf6b1e9c7d) fix conflicts - [`18a54a4`](https://github.com/run-llama/llama_deploy/commit/18a54a41e638e5fa3eef8972a4a3941f5f254028) add union discriminant to the existing config models ### 📊 Changes **11 files changed** (+166 additions, -33 deletions) <details> <summary>View changed files</summary> 📝 `llama_deploy/apiserver/config_parser.py` (+22 -2) 📝 `llama_deploy/apiserver/deployment.py` (+48 -10) 📝 `llama_deploy/message_queues/apache_kafka.py` (+7 -8) 📝 `llama_deploy/message_queues/aws.py` (+3 -1) 📝 `llama_deploy/message_queues/rabbitmq.py` (+5 -2) 📝 `llama_deploy/message_queues/redis.py` (+6 -3) 📝 `llama_deploy/message_queues/simple.py` (+5 -4) 📝 `tests/apiserver/conftest.py` (+14 -0) 📝 `tests/apiserver/data/example.yaml` (+5 -0) 📝 `tests/apiserver/test_config_parser.py` (+3 -0) 📝 `tests/apiserver/test_deployment.py` (+48 -3) </details> ### 📄 Description Add a section in the deployment config file to define the message queue to use. Notes: - a string literal field `type` was added to the existing config models so that we can use it to tell Pydantic what's the right model to use when loading `message-queue` from the config The format will be: ```yaml message-queue: type: simple # this section depends on the type of the message queue and will be validated accordingly host: "127.0.0.1" port: 8001 ``` --- <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:03 -05:00

yindo closed this issue

2026-02-16 01:17:03 -05:00

yindo referenced this issue

2026-02-16 01:17:16 -05:00

[PR #365] [MERGED] refact: Use the Python SDK in the CLI implementation #417

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: run-llama/llama_deploy#365