-
Notifications
You must be signed in to change notification settings - Fork 387
feat: allow users to add env vars to dynamo deployment #862
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/ai-dynamo/dynamo/blob/main/examples/llm/configs/disagg.yaml#L35
^ If we added an envs section at the line ive linked above, it will set an env variable for that service at runtime. Futhermore, it's scoped specifically to that service. We can also use a cli arg to do the same. Can you test the following first?
dynamo serve ... --ServiceA.ServiceArgs.envs.HF_CACHE=$KEY
dynamo deploy ... --ServiceA.ServiceArgs.envs.HF_CACHE=$KEY
It doesn't seem to work 😬 (I'm working with agg.yaml for the record). I added an envs section to the config file then ran
|
Co-authored-by: mohammedabdulwahhab <furkhan324@berkeley.edu> Signed-off-by: hhzhang16 <54051230+hhzhang16@users.noreply.github.com>
Overview:
Allow users to add environment variables to their Dynamo deployments
Details:
Allow support for env variables (using
--env
)Where should the reviewer start?
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)