element-hq / element-hq/dendrite

Configuration by Environment Variables

Open
#2,591 8 comments 2 reactions 0 assignees View on GitHub
C-Config long term T-Enhancement
Dominant language
Go
Stars
965
Forks
101
PR merge metrics
No merged PRs in 30d

Description

*This issue was originally created by [**@genofire**](https://github.com/genofire) at .*

**Problem:**

In a K8s it is really common to run dependencies by other applications like an database operator (zalando's postgres operator). Which generates k8s secrets, for credentials like username and password.

It would be nice to use them directly (instatt of generate configfiles, stored in new k8s secrets with helm or other tooling). Therefore exists the possibility to use envFromSecrets in k8s deployments.

**Description/Solution:**

So please make it possible to give dendrite configuration parameters with env variables.

**Implemented Suggested:**

Maybe you like to use the golang library [viper](https://github.com/spf13/viper) and cobra from spf13 for it.

Contributor guide

Open the contributing guide

Research direction

The issue names no Dendrite files, tests, or configuration entry points. Start by locating how configuration is loaded and compare that with Kubernetes envFromSecrets and the suggested viper/cobra approach; done means the requested configuration parameters can be supplied through environment variables without generated config files.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.