I'm envisioning something like patch files in an RPM - things that can easily come and go depending on what needs to be done for a particular release.  In this case, instead of patch files, these would be short perl or shell scripts.  These would be invoked once or once per instance.

One way would be to have a large script which would be edited for each release, adding or deleting code as needed.  This is the way it worked in the past - the file quickly becomes "unruly".  However, we would only have to touch Makefile.am once to add the upgrade script.

Another way would be to have small scripts that could come and go with each release.  The disadvantage is that we would be constantly adding/deleting items from Makefile.am.  This is what I would prefer.

Before invoking the update scripts, the code would create some sort of context, containing information about the config directory, each instance, and an identity and credentials that can be used to manage each instance.  For example, when you run setup-ds-admin.pl -u, it uses the uid=admin identity and asks for the password, then uses that identity to manage each instance.  However, in the case where there is just the base ds package, we would need some way to ask or specify the identity for each instance.  For the UI, I don't think there's any way around just simply asking for the username and password for each instance (we can default the username to directory manager or the last value specified).  For .inf file usage, I was thinking about adding a new section - [slapd-instancename] - in which you could specify the RootDN and RootDNPwd.

--
389-devel mailing list
389-devel@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-devel