Pack-level environment varaibles
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
It would be helpful to have access to a set of environment variables at the pack level, that are generated at runtime, to guarantee they will be there. Something like a pack.env file that could be easily configured on the fly, as @nmaludy mentioned in slack today. This feature would allow existing python scripts that rely on the environment to be converted to actions without a major refactor. The only solution I'm currently aware of is storing these variables in a data store somewhere -- requires a major refactor of existing code to access them and feels like there should be a better solution.
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
No files, tests, or entry points are identified. Begin by tracing how pack and action environments are currently configured, then define the runtime generation and configuration behavior for a pack-level environment file; done should include a clear way for existing Python scripts to access the variables without a major refactor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100