Thanks Howard, I am already doing this for the default configuration. I was hoping I could get around fetching secrets and importing changes at run time.
-----Original Message----- Subject: Re: Environment variable in slapd config
Marc Roos wrote:
Indeed. Ansible is just a tool you should use for the fitting job. Afaik I only have to set a few variables and I do not have in the hundreds of services. But I would not mind looking at your Dockerfile to see how you prepare the image.
The ceph mailing list is 'full' of people using ansible, and then whining on what to do, and how to fix things when something does not work. Because they do not know how and where things are configured. All these 'easy' tools are like these higher level programming languages. They just lower the threshold for the 'bunglers' to enter an area of expertise, they were not able to enter before.
-----Original Message----- Subject: Re: Environment variable in slapd config
Probably the original poster wanted to set several env vars and use them as distinct RID values for multiple syncrepl directives. This is a common pattern for poor man's config management.
Ciao, Michael.
For this use case the simplest approach is to start with a template file that uses shell variables and just let the shell do the substitution for you. This is exactly what the OpenLDAP test suite does for its own config files.
If you need to get fancier use sed or awk. These are basic Unix admin questions and have nothing to do with OpenLDAP.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/