Fix LDAP Ppassword env variable #182

Merged
techknowlogick merged 1 commits from fix-ldap-password into master 2021-06-15 21:08:00 +00:00
Member

Fixes: #179

Fixes: #179
zeripath approved these changes 2021-06-15 20:28:52 +00:00
luhahn force-pushed fix-ldap-password from e2047afa44 to 5de9034e6d 2021-06-15 20:29:00 +00:00 Compare
techknowlogick approved these changes 2021-06-15 21:07:30 +00:00
techknowlogick merged commit e3b03cd61a into master 2021-06-15 21:08:00 +00:00
Contributor

TBH, this seems to not fully fix the regression or at least not fully finalize this feature. Previous to that PR, the admin user was created by using the LDAP bind settings (if I'm getting this right). Now with the correct environment variable for the LDAP credentials no admin user will be created when using existingSecret for the admin account. This feature was introduced with c49dc047a4 as well, I assume that we should fix this, too. Right now the admin account is only created when using inline credentials in values.yaml (see c49dc047a4/templates/gitea/init.yaml (L43))

TBH, this seems to not fully fix the regression or at least not fully finalize this feature. Previous to that PR, the admin user was created by using the LDAP bind settings (if I'm getting this right). Now with the correct environment variable for the LDAP credentials no admin user will be created when using `existingSecret` for the admin account. This feature was introduced with c49dc047a498973920e6743fa6c330fd2f81dd47 as well, I assume that we should fix this, too. Right now the admin account is only created when using inline credentials in `values.yaml` (see https://gitea.com/gitea/helm-chart/src/commit/c49dc047a498973920e6743fa6c330fd2f81dd47/templates/gitea/init.yaml#L43)
Contributor

Oh no... too late.

Oh no... too late.
justusbunsi added the
kind
bug
label 2021-06-30 10:18:40 +00:00
justusbunsi added this to the Release 4.0.0 milestone 2021-06-30 10:18:46 +00:00
Sign in to join this conversation.
No description provided.