[389-devel] [lib389] dsconf plugins support and cmd line design

Hello,

I'm going to add support for the memberOf plugin into the dsconf tool. However, because this is going to be the first plugin to be configurable through lib389, design decisions will affect all future plugins to be supported.

I'd like thoughts on which approach would be more convenient for an admin.

Right now, there's an initial general design for all plugins here: https://pagure.io/lib389/blob/master/f/lib389/cli_conf/plugin.py

This suggests that we do things the following way:

1. "dsconf instance plugin enable" and then it prompts us to enter the dn of the plugin to enable.
2. "dsconf instance plugin config" and then it prompts again for a dn and displays configuration options *specific* to that plugin

I think it might be more handy to avoid additional prompts and directly do things like the following:

dsconf instance plugin memberof enable
dsconf instance plugin memberof fixup

However, this way we will end up with very long commands.
eg.
dsconf instance plugin memberof config modify "memberofattr" "memberOf2"

which is huge.

With the second approach it's easier to write scripts based on dsconf though.

Any thoughts on this?

Thanks in advance,

Ilias