It would be nice if dsconf could enable/disable a plug-in by only passing the plug-in name to the command instead of the full DN.
389-ds-base-1.4.0.16-20180829gitd6616221a.fc28.x86_64
To enable:
# dsconf -D 'cn=Directory Manager' ldap://server.example.com plugin enable "cn=Retro Changelog Plugin,cn=plugins,cn=config"
To disable:
# dsconf -D 'cn=Directory Manager' ldap://server.example.com plugin disable "cn=Retro Changelog Plugin,cn=plugins,cn=config"
You must pass the full DN of the plug-in to the command. If you only use the plug-in's name, it fails:
# dsconf -D 'cn=Directory Manager' ldap://server.example.com plugin enable "Retro Changelog Plugin" Enter password for cn=Directory Manager on ldap://server.example.com: Error: {'desc': 'Invalid DN syntax', 'info': 'invalid dn'}
Enabling/disabling a plug-in should work by only passing the plug-in's name's to the command.
This already works for "dsconf plugin get":
# dsconf -D 'cn=Directory Manager' ldap://server.example.com plugin get "Retro Changelog Plugin"
@spichugi This could be pretty easy? But I think we need to template out all the plugins in plugins.py
Thanks for the suggest @mmuehlfeldrh :)
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
@spichugi This could be pretty easy? But I think we need to template out all the plugins in plugins.py Thanks for the suggest @mmuehlfeldrh :)
Yeah, shouldn't be very hard and it should be done. Specifying the full DN is not very user friendly
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4.3 (was: 1.4.0)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2994
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.