Proposal: Provide a way for the user to optionally, in addition to the password, set the bcrypted-version of the password. If this is set (default can be unset, so we do not change any of the current behavior), then take this, instead of running htpasswd.
My workaround for now is to completely write the users.js myself (copied from your version), which is not ideal.
The
provisioner
user's password is bcrypted and generated viahtpasswd
(see also: https://github.com/Ontotext-AD/graphdb-helm/blob/main/files/config/users.js#L19). It would get another bcrypt every time Helm renders.Proposal: Provide a way for the user to optionally, in addition to the password, set the bcrypted-version of the password. If this is set (default can be unset, so we do not change any of the current behavior), then take this, instead of running
htpasswd
.My workaround for now is to completely write the users.js myself (copied from your version), which is not ideal.