VisionSystemsInc / VisionSystemsInc/vsi_common
SHA environment
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8
- Forks
- 9
- Avg merge
- 36m
- Merged PRs (30d)
- 1
Description
Get output of environment variables (and local variables?) and sha them
- Determine list of variables that shouldn't be include, like UID, pwd, , BASH_SOURCES, LINENO, BASH*, etc...
- Sha variables and values
This is a stepping stone to running docker-compose config once, and caching the result. The environment can be used to determine cache miss. Since Just-docker-compose creates a randomly named file and used env vars to generate it, the command executed is not a sufficient cache miss check, it will always be different or changing env vars will cause different behavior. And its always posssible that multiple calls to Just-docker-compose will have different environments. So the args to Just-docker-compose + env sha should make a decent cache miss check
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
Start with the Just-docker-compose entry point mentioned in the issue and trace how its generated file and environment are used for caching. Define the variables to exclude, produce a stable SHA from the remaining variables and values, and verify that changed environments produce distinct cache checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100