Any reason why LDAP_BASE_DN is not setable via ENV

[EugenMayer]

For me it was convinient to set the LDAP_BASE_DN via the ENV file, since the image supports it ( see https://github.com/EugenMayer/docker-rancher-extra-catalogs/blob/master/templates/openldap/26/docker-compose.yml#L14 )

Are there any particular reasons you do not support setting this out of the box, are there technical issues you are trying to avoid?

Great to have your insight / design decision here, thanks!

[jp-gouin]

Hi @EugenMayer

The chart is currenlty under a large refractoring to match best practices and be more user friendly to use. You can track/contribute under the branch https://github.com/jp-gouin/helm-openldap/tree/refractor-chart.

I hope to get some time soon to finish the work

[jp-gouin]

Hi @EugenMayer , You probably figure something else by the time but I’d still want to answer your question ☺️ from the osixia openldap documentation LDAP_DOMAIN: Ldap domain. Defaults to example.org LDAP_BASE_DN: Ldap base DN. If empty automatically set from LDAP_DOMAIN value. Defaults to (empty)

Both are possible but it’s true that I choose the LDAP_DOMAIN approach , a little bit more natural but that just my opinion. It will be complicated now that I’ve done the refactoring to use LDAP_BASE_DN because I use LDAP_DOMAIN variable in the helper to unit global variable used by sub charts .

what did you want to achieve and why LDAP_DOMAIN wasn’t an option for you ?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.