Add envsubst so dns-conf credentials can be added from container environment variables
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- dockerfile
- Domain
- devops
Research direction
Start by tracing the container-start path and inspect /config/dns-conf/cloudflare.ini, along with the compose or .env inputs mentioned in the issue. Check how envsubst is available in the image and whether other DNS-provider files follow the same pattern. Done means supported environment variables populate configuration at startup without requiring duplicate credentials in tracked files.
Written by the indexing model from the issue text.
Description
Desired Behavior
Instead of editing /config/dns-conf/cloudflare.ini to hardcode email and API key/token and drag that sensitive credentials through Git (my case), I'd like to have envsubst triggered on container start that takes environment variables like EMAIL and CF_API_TOKEN and replaces those environment variables in files.
Considering user already adds these values to their compose or .env file, it makes little sense to have same creds added in multiple locations if they can be added automatically.
I'm guessing this behavior is applicable to other DNS providers as well.
Current Behavior
The user needs to add the same environment variable values multiple times, once in compose file and second time to cloudflare.ini.
Alternatives Considered
Manually maintaining the same values in multiple places and accidentally checking sensitive creds to git for people who version their setups.
- Dominant language
- Dockerfile
- Stars
- 3.7k
- Forks
- 275
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from linuxserver/docker-swag
-
no-issue-activity
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linuxserver/docker-swag#616 · 12 comments ·
-
[BUG] "chmod: changing permissions of '/XXX': Bad address" error message (QNAP)May be free again A pull request for this issue was closed without being merged. Openbug upstream issue work-in-progress
Difficulty 4/5 3-5 days Newbie friendliness 45/100
linuxserver/docker-swag#514 · 74 comments ·
-
Support custom ACME serversPossibly taken @nemchik claimed this 626 days ago. Openawaiting-approval
linuxserver/docker-swag#186 · 23 comments · 8 reactions · 1 assignee ·
All issues in linuxserver/docker-swag
Similar issues
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Bug]: multi-arch `vgpu-device-manager` image digest not pinned in OLM bundlePossibly taken @MrBeldum claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NVIDIA/gpu-operator#3012 · 1 comment ·
Maintainers usually reply within 1 day
-
bug customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MagnaCapax/PMSS#1011 ·
Maintainers usually reply within 5 days
-
[v2 Bug] latest-wrangler fails with a misleading TypeError when the GitHub API call failsPossibly taken @GertL claimed this today. Openbug engine:v2 status:triage triage type:bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
[CI] Core CI doesn't run for changes to amoro-format-lance (and amoro-web)Possibly taken @MarkAlex1234 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 2 days