zalando / zalando/postgres-operator
User Secret should contain connection string
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Type of issue? feature request
It would be nice, to have also an key with an psql connection string in it, so that this value could easy reuse in application or helm-charts.
affected function generateSingleUserSecret - code is here:
secrets should contain best values (with tls if enabled and namespace in url)
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
Start in pkg/cluster/k8sres.go at generateSingleUserSecret and inspect how the existing user Secret values are assembled. Check the surrounding secret-generation code and determine the expected psql connection-string format, including TLS settings and the namespace in the URL. Done means the Secret also exposes the requested reusable connection-string value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100