Entrypoint:envsubst skip if already done
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 1.8k
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
Envsubst happens every time you start the container. Wouldn't it be better if it passed after finding file already touched by it?
This overwrites any manual changes made to the envsubst output conf file.
Example use case:
- create generic template
- run envsubst
- add ssl
- don't lose ssl when container restarts
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 at the container entrypoint and inspect the envsubst path described in the issue. Verify the behavior by substituting a template, making a manual SSL-related change to the output configuration, and restarting the container; done means the existing output is preserved instead of being overwritten.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100