Add environment variables to deployment definition #119

New Issue

2026-02-16T01:15:51-05:00

yindo commented

2026-02-16 01:15:51 -05:00

Originally created by @masci on GitHub (Oct 15, 2024).

Originally assigned to: @nerdai on GitHub.

At the moment the only way to pass env vars to a running instance of Llama Deploy is through setting them before starting the process, which is not practical in case of a remote installation or docker containers.

We should add the option to declare the environment variables needed by each service like this:

services:
  test-workflow:
    name: Test Workflow
    env:
        OPENAI_API_KEY: "secret!"
    source:
      type: git
      name: https://github.com/run-llama/llama_deploy.git
    path: tests/apiserver/data/workflow:my_workflow

then the Control plane would propagate the env var when spinning up the service.

Originally created by @masci on GitHub (Oct 15, 2024). Originally assigned to: @nerdai on GitHub. At the moment the only way to pass env vars to a running instance of Llama Deploy is through setting them before starting the process, which is not practical in case of a remote installation or docker containers. We should add the option to declare the environment variables needed by each service like this: ```yaml services: test-workflow: name: Test Workflow env: OPENAI_API_KEY: "secret!" source: type: git name: https://github.com/run-llama/llama_deploy.git path: tests/apiserver/data/workflow:my_workflow ``` then the Control plane would propagate the env var when spinning up the service.

yindo added the enhancement topic:apiserver labels 2026-02-16 01:15:51 -05:00

yindo closed this issue

2026-02-16 01:15:51 -05:00

yindo referenced this issue

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

[PR #119] [MERGED] [fix] lazily init object index to avoid embeddings init #276

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: run-llama/llama_deploy#119