oxidecomputer / oxidecomputer/omicron-package
Ability to pass environment variables
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
It would be really nice to have the ability to pass environment variables to the packages we're building. This will be specifically helpful when wanting to deploy for different environment types during the development cycle.
For example, today some of our smf directories sometimes have several configuration subdirectories. Instead of having several copies of the same config file with different values, it'd be really nice to be able to set these values as environment variables at build time
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are identified. Start by tracing the package build flow and how SMF configuration directories are assembled; done should allow build-time environment variables to provide configuration values without maintaining duplicate config files for each environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100