Wrong database name in Nextcloud initContainer
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
In the deployment template, here:
https://github.com/nextcloud/helm/blob/master/charts/nextcloud/templates/deployment.yaml#L274
The commands are using %s-mariadb or %s-postgresql.
Why not use the variable ${MYSQL_HOST} and ${POSTGRESQL_HOST} ?
I tried a deployment with a primary/secondary MariaDB cluster, and the host should then be nextcloud-mariadb-primary instead of nextcloud-mariadb.
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
Open charts/nextcloud/templates/deployment.yaml around line 274 and inspect the initContainer commands and the MYSQL_HOST and POSTGRESQL_HOST variables. Done means the commands use the configured database host values so clustered MariaDB or PostgreSQL deployments resolve the correct primary or service hostname.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100