>> As sysadmin I create a lot of script to install/manage
>> and is confusing having commands that change that often.
You may find it "more stable" to use lib389 directly rather than the
CLI then. I think the team should talk about the CLI having an
"interface guarantee", and today I don't think I personally would
want to commit to that (but the team hasn't decided on this). I
still see room to change and grow the CLI in ways that may be
breaking, but the core of lib389 today seems "pretty stable".
I understand your recommendation but I don't think I'm going to do that, and I
think I "shouldn't" do that.
my job as sysadmin is installing, managing, mantaining and monitoring, and dsconf wrapping
is just what I need.
If I have, for example, a command that tells me if a drive is out of space I don't
expect to change that command over the years on different linux systems with different
I understand that 389 is under heavy refactoring these last years, I'm just a little
bit tired of version conditionals in my recipes (and by the way, I can't find an easy
method to check the version with dsconf/dsctl, worth a feature request?).
so taking my own example I just expect that `dsconf instance plugin retro-changelog
enable' is still valid a year/version later.
again, please take my point of view as a frustrated admin with too many tasks to do and
too little beers to take on my free time (everything is closed right now in Mallorca :P)
-- Institut Mallorqui d'Afers Socials. Aquest missatge, i si escau, qualsevol fitxer
annex, es dirigeix exclusivament a la persona que n'es destinataria i pot contenir
informacio confidencial. En cap cas no heu de copiar aquest missatge ni lliurar-lo a
terceres persones sense permis expres de l'IMAS. Si no sou la persona destinataria que
s'hi indica (o la responsable de lliurar-l'hi) us demanam que ho notifiqueu
immediatament a l'adreca electronica de la persona remitent. Abans d'imprimir
aquest missatge, pensau si es realment necessari.