Make providing custom envronment variables easier
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 113
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
Currently, customers have no easy way to provide custom environment variables to our executors in our recipes code. The solution involves modifying the code in virtual environment where nemo is installed.
Ideally, the installed nemo code shouldn't be modified and we should provide users an easier way to pass the environment variables to the executors.
This feature request is created as a result of this inquiry:
https://requests-navigator.atlassian.net/jira/servicedesk/projects/NFS/queues/custom/237/NFS-395
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the recipes code configures executors and where custom environment variables currently require changes to the installed NeMo code. Define the supported input path and verify that users can provide variables without modifying the virtual-environment installation; the issue provides no specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100