Add Docker Secrets/Configs support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 180
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
See Docker documents:
Secrets have several advantages over inserting credentials into environment variables, and are considered best practice for Swarm setups.
Can this be added please? Many images implement this via either allowing environment variables to have a suffix like __FILE to specify the path of the secret/config, which is loaded inside the app.
Right now this can be worked around with a custom entrypoint, but that requires updating if the Dockerfile entrypoint or command is ever altered. Edit: This cannot be worked around as it turns out, as I forgot that new containers are spun up to perform the actual backups.
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 linked Docker Swarm secrets and configs documentation, then trace how stack services and the new containers used for backups are created. Determine how secret/config sources and environment-variable file suffixes should be represented and propagated, including changes needed when the Dockerfile entrypoint or command changes. Done means backup containers can consume Docker secrets or configs without a custom entrypoint, with behavior covered by the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100