Lib389 has a legacy Entry interface. It's implemented in a really complex and difficult to understand manner. This interface is deprecated, and we have wanted to remove it for sometime. In wanting to remove it, we have tried to ask people to stop using the _s apis because it adds more techdebt on an interface we don't want.
Developers and QE want to be able to control certain ldap operations though. They want to use the _s apis. But this would make it harder and harder to remove this piece of techdebt.
I have resisted people using the _s ldap apis because I don't want more usage of Entry, but we also can't remove it easily because we would break some legacy tests.
As a middle ground it was suggested that:
This way people could use the ldap calls on dirsrv they want for tests, and we move closer to identifying and removing the Entry api.
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.2 - Issue tagged with: lib389
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4 backlog (was: 1.4.2)
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/3656
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.