@firstyear
William, what do you have in mind about configuring this?

There are actually only 3 attributes; linktype, managedtype, linkscope. Many instances of the plugin can be created though. The global plugin configuration entry can just be enabled/disabled so nothing interesting there.

I was thinking of something like the following, but I'd like some feedback/thoughts.

dsconf ... linkedattrs list # list all plugin instances (DNs only)
dsconf ... linkedattrs list full # list all instances along with their config
dsconf ... linkedattrs "rdn" show  # display this instance; rdn can be "Manager Link" for example
dsconf ... linkedattrs "Manager Link" scope # get scope
dsconf ... linkedattrs "Manager Link" scope "ou=people2,dc=example,dc=com" # set scope

We also need a way to create new instances of the plugin. The following would probably do?

dsconf ... linkedattrs new -cn "Manager Link" -l "direct Report" -m "manager" -scope "dc=example,dc=com"

could translate to:

dn: cn=Manager Link,cn=Linked Attributes,cn=plugins,cn=config
objectClass: top
objectClass: extensibleObject
cn: Manager Link
linktype: directReport
managedtype: manager
linkscope: dc=example,dc=com

Well, after re-reading all the above, I actually have a concern. Is all this really simpler than applying ldifs directly?

This plugin isn't a high priority to enable, so we can revisit this problem later. I suspect this is in the same basket as uiduniq where we need to think about a configuration re-write to make it nice.