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

[PR #470] [MERGED] feat: add config profiles to llamactl #485

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/470
Author: @masci
Created: 2/19/2025
Status: ✅ Merged
Merged: 2/28/2025
Merged by: @masci

Base: main ← Head: massi/config-profiles

📝 Commits (4)

  • aec3599 feat: add config profiles to llamactl
  • 9368e4c add unit tests
  • a9d17ef use a test config file in tests
  • c1a581d add platformdirs dependency

📊 Changes

13 files changed (+335 additions, -43 deletions)

View changed files

📝 llama_deploy/cli/__init__.py (+46 -5)
📝 llama_deploy/cli/deploy.py (+11 -4)
➕ llama_deploy/cli/internal/config.py (+42 -0)
📝 llama_deploy/cli/run.py (+9 -4)
📝 llama_deploy/cli/sessions.py (+9 -4)
📝 llama_deploy/cli/status.py (+9 -4)
📝 poetry.lock (+127 -18)
📝 pyproject.toml (+1 -0)
📝 tests/cli/conftest.py (+28 -3)
➕ tests/cli/data/config.yaml (+9 -0)
➕ tests/cli/internal/__init__.py (+0 -0)
➕ tests/cli/internal/test_config.py (+38 -0)
📝 tests/cli/test_cli.py (+6 -1)

📄 Description

This PR adds support for config profiles to llamactl. From now on, llamactl will store a configuration file with the following format:

default:
  insecure: true
  server: http://localhost:4501
  timeout: 10.0

prod:
  insecure: false
  server: http://example.com:8080
  timeout: 120.0

Users can specify what profile to use by passing its name with the option --profile. The default profile will be selected when --profile is not used.

🔄 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/470 **Author:** [@masci](https://github.com/masci) **Created:** 2/19/2025 **Status:** ✅ Merged **Merged:** 2/28/2025 **Merged by:** [@masci](https://github.com/masci) **Base:** `main` ← **Head:** `massi/config-profiles` --- ### 📝 Commits (4) - [`aec3599`](https://github.com/run-llama/llama_deploy/commit/aec35997854d30ab634251b7b086a43193821e15) feat: add config profiles to llamactl - [`9368e4c`](https://github.com/run-llama/llama_deploy/commit/9368e4cc4402ea8cf78953e3d0994c61412c27f7) add unit tests - [`a9d17ef`](https://github.com/run-llama/llama_deploy/commit/a9d17ef54fff4c54a97f92b10fb6297d020c81bf) use a test config file in tests - [`c1a581d`](https://github.com/run-llama/llama_deploy/commit/c1a581d28accac8a265cb7c4466051cb73791e8f) add platformdirs dependency ### 📊 Changes **13 files changed** (+335 additions, -43 deletions) <details> <summary>View changed files</summary> 📝 `llama_deploy/cli/__init__.py` (+46 -5) 📝 `llama_deploy/cli/deploy.py` (+11 -4) ➕ `llama_deploy/cli/internal/config.py` (+42 -0) 📝 `llama_deploy/cli/run.py` (+9 -4) 📝 `llama_deploy/cli/sessions.py` (+9 -4) 📝 `llama_deploy/cli/status.py` (+9 -4) 📝 `poetry.lock` (+127 -18) 📝 `pyproject.toml` (+1 -0) 📝 `tests/cli/conftest.py` (+28 -3) ➕ `tests/cli/data/config.yaml` (+9 -0) ➕ `tests/cli/internal/__init__.py` (+0 -0) ➕ `tests/cli/internal/test_config.py` (+38 -0) 📝 `tests/cli/test_cli.py` (+6 -1) </details> ### 📄 Description This PR adds support for config profiles to `llamactl`. From now on, `llamactl` will store a configuration file with the following format: ``` default: insecure: true server: http://localhost:4501 timeout: 10.0 prod: insecure: false server: http://example.com:8080 timeout: 120.0 ``` Users can specify what profile to use by passing its name with the option `--profile`. The `default` profile will be selected when `--profile` is not used. --- <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:05 -05:00
yindo closed this issue 2026-02-16 02:15:05 -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#485
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?