Non-Internal Database Prompts Admin creation window on deployment and subsequent updates
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
I have been experimenting deployment with various settings and one of the biggest pain points I am dealing with is using either an external database or mariadb.
I have a postgres database setup and on deployment, nextcloud has access. I can see all the tables it created and the admin user is in the oc_users table, generated from the existingSecret. However, accessing nextcloud for the first time still loads the admin creation window. Furthermore, if I make changes and run helm update I again get the admin creation window.
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 a deployment with an external PostgreSQL or MariaDB database and an existingSecret, then inspect how the Helm chart handles the existing admin user during initial access and subsequent updates. Done means the admin creation window does not reappear after deployment or a Helm update when the database and secret are already populated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, mariadb, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100