Issue with semicolons in Postgres passwords for Connect and Package Manager
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
When there is a semicolon in the password for Connect or Package Manager (either passed in via --set in helm or in the values file), the services fail to connect to the Postgres database. Taking out the semicolon (and changing the password on the Postgres side) then works without issue.
I think its an issue in translating the values to the config files. If I run Connect and Package Manager outside of k8s and put the password with a semicolon in the configs, it works without issue.
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 by reproducing the failure with a semicolon in the Postgres password, once supplied through Helm --set and once through the values file. Compare the generated config for Connect and Package Manager with the configuration that works outside Kubernetes; done means both services connect successfully without changing the password.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100