janeczku/rancher-letsencrypt

Support for reading config items from Rancher secrets

Open

#76 opened on May 9, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (110 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (324 stars)
PR merge metrics
 (PR metrics pending)

Description

It would be great if rancher-letsencrypt could read 'secret' config options like API keys from values passed by the Rancher secrets mechanism. Perhaps update getEnvOption so it:

  • Check if the environment variable is set, if so use that
  • Check if there is a file with the variable name in /run/secrets, if so use that

Contributor guide

Research direction
Modify the `getEnvOption` function to first check if a file with the environment variable name exists in `/run/secrets`, and if so, read its contents as the value; otherwise fall back to the environment variable. Ensure to handle file reading errors gracefully.
Tech stack
go
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Goreading environment variablesfile I/O
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70