Ability to use existing secret for config
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 41
- Forks
- 45
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 37
Description
Hi,
This looks promising!
I see you already support setting some "secret" environment variables via values.
In my case, I'd like to be able to configure these and additional environment variables, for example:
GITHUB_TOKEN
WEBLATE_AUTH_LDAP_SERVER_URI
I would also like to do this without needing to put them in my values.yaml file.
...for example by adding a secret beforehand and configuring this chart to use my predefined secret instead of creating a new one.
As this chart is using postgres, here's an example of how the postgres chart either creates a secret or uses an existing one:
https://github.com/helm/charts/blob/12a061a/stable/postgresql/templates/_helpers.tpl#L210-L232
What do you think, would you be open to supporting something like this?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
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
Read charts/weblate/templates/deployment.yaml and charts/weblate/templates/secret.yaml first, then compare the existing secret pattern with the requested environment variables and the linked PostgreSQL example. Done means the chart can use a predefined secret for the current and additional configuration values without requiring those secrets in values.yaml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100