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

[PR #454] [MERGED] Add Solace Message Queue To API Reference Documents #476

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/454
Author: @alimosaed
Created: 2/10/2025
Status: ✅ Merged
Merged: 2/10/2025
Merged by: @masci

Base: main ← Head: main

📝 Commits (10+)

  • e33ef76 Ap/add solace event broker (#1)
  • b26d231 Merge branch 'main' into main
  • f9b949d fix: rebuild the poetry.lock
  • 4e5b72e fix: resolved conflicts
  • cde00b0 Merge branch 'main' into main
  • 767d2aa Merge branch 'main' into main
  • 2949900 feat: addressed comments. 1-move configs to the Solace script 2-fix a few bugs 3- update type checking
  • ce8085d Merge branch 'main' into main
  • 3a7acf9 feat: refactor codes and read configurations from pydantic
  • 8ab0cf4 feat: pull latest updates

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

➕ docs/docs/api_reference/llama_deploy/message_queues/solace.md (+3 -0)

📄 Description

What is the purpose of this change?
Add Solace message queue to the API reference documents.

How is this accomplished?
Added the Solace message queue path to the Solace.md file to automatically generate documents.

Anything reviews should focus on/be aware of?
Nothing

🔄 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/454 **Author:** [@alimosaed](https://github.com/alimosaed) **Created:** 2/10/2025 **Status:** ✅ Merged **Merged:** 2/10/2025 **Merged by:** [@masci](https://github.com/masci) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (10+) - [`e33ef76`](https://github.com/run-llama/llama_deploy/commit/e33ef7656070aaea337889f17234dc004b55fed9) Ap/add solace event broker (#1) - [`b26d231`](https://github.com/run-llama/llama_deploy/commit/b26d231d809b2bf892ebb630dc051ca50fb927bf) Merge branch 'main' into main - [`f9b949d`](https://github.com/run-llama/llama_deploy/commit/f9b949d9fa5ca24e687631d8cb4c8ea3fbe70be8) fix: rebuild the poetry.lock - [`4e5b72e`](https://github.com/run-llama/llama_deploy/commit/4e5b72edcc8f0b59cb4dc56872873d6a45546e5d) fix: resolved conflicts - [`cde00b0`](https://github.com/run-llama/llama_deploy/commit/cde00b0177be96253cdf57565f6ce361025f2af3) Merge branch 'main' into main - [`767d2aa`](https://github.com/run-llama/llama_deploy/commit/767d2aa83848025ebe9929f1d2d1f2426523ab95) Merge branch 'main' into main - [`2949900`](https://github.com/run-llama/llama_deploy/commit/29499001c869901bb00f0e4670ea7250f4a4fe12) feat: addressed comments. 1-move configs to the Solace script 2-fix a few bugs 3- update type checking - [`ce8085d`](https://github.com/run-llama/llama_deploy/commit/ce8085d5aeb4f1dc3c6af2a5134f52adc0889bbe) Merge branch 'main' into main - [`3a7acf9`](https://github.com/run-llama/llama_deploy/commit/3a7acf913eb3950c522c51974b449f2528f16496) feat: refactor codes and read configurations from pydantic - [`8ab0cf4`](https://github.com/run-llama/llama_deploy/commit/8ab0cf4588aa848a8c7a2107c860cf7f47590f73) feat: pull latest updates ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/docs/api_reference/llama_deploy/message_queues/solace.md` (+3 -0) </details> ### 📄 Description **What is the purpose of this change?** Add Solace message queue to the API reference documents. **How is this accomplished?** Added the Solace message queue path to the Solace.md file to automatically generate documents. **Anything reviews should focus on/be aware of?** Nothing --- <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:02 -05:00
yindo closed this issue 2026-02-16 02:15:02 -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#476
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?