#50224 Create warnings and disincentives for using deprecated lib389 apis
Closed: wontfix 5 years ago by firstyear. Opened 5 years ago by firstyear.

Issue Description

Recently I have noticed a large increase in people using apis of lib389 that should not be used. Due to the nature of python, it's really just plain hard to discourage people from using these.

Right now, we are currently sitting on a really weird tech-debt of how DirSrv is designed. To fix this will be a large effort, but step one is to create behaviours that teach people not to use this.

Specifically, this will target:

  • all _s inherited ldap functions
  • Entry init
  • getEntry()

There however, must be an "escape" hatch to allow lib389 internal to use these without penalty.

I can't continue to blame people for doing the wrong thing, where our library plainy allows itself to be used incorrectly. We need our library to prevent at an api level, incorrect usage.


Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

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/3283

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata