Rich Megginson wrote: > Instead of an argument checker, what if there were a way to do a "dry-run" > of the ldapmodify command, that would show you what the command would do? > Would that satisfy the customer's requirement? adding/modifying/deleteing [attribute/entry] warning: attribute /policy / role doesnt exist
Set it to FUTURE just for the record. See also this comment. https://bugzilla.redhat.com/show_bug.cgi?id=1271054#c10
Metadata Update from @nhosoi: - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/1727
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.
Login to comment on this ticket.