Repository navigation
mariadb: users.*.password is required, unlike postgres and mongodb which generate one #3395
Description
The mariadb values schema marks password required for every entry under users, so a user without a password fails helm validation:
- at '/users/app': missing property 'password'
Postgres and mongodb take the opposite approach — password is optional and the chart generates one when it's absent.
This breaks any flow built on platform-generated credentials: the caller declares a user and reads the generated password back from the credentials secret. Works for postgres/mongodb, fails for mariadb.
Suggested fix: make password optional and generate it the way the sibling charts do.
Activity
dosubot commentedon Jul 21, 2026
This looks like a valid inconsistency. The MariaDB values schema explicitly marks
passwordas required for user entries [1], while both PostgreSQL [2] and MongoDB [3] leave it optional — MongoDB even documents it as"(auto-generated if omitted)".Interestingly, MariaDB's
secret.yamltemplate already has the auto-generation logic to handle missing passwords [4]:{{- if $u.password }} {{- $_ := set $passwords $user $u.password }} {{- else if not (index $passwords $user) }} {{- $_ := set $passwords $user (randAlphaNum 16) }} {{- end }}So the template is ready to generate passwords when omitted — the schema's
requiredconstraint is just preventing that code path from ever being reached. The fix should be straightforward: remove"password"from therequiredarray in the MariaDB values schema.To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
pranav767 commentedon Jul 29, 2026
I'd like to work on this issue.