#1747 Refactor subdomain interfaces
Closed: Fixed None Opened 9 years ago by simo.

The subdomain code was sort of rushed in and the interfaces are not optimal.

In particular one change, that there are multiple 'domains' in a single sysdb database was not properly handled in the sysdb itself.

The sysdb had various assumptions based on 1 file 1 domain that need to be changed architecturally to avoid ripple issues.

One of the first things to change is that sysdb API now need to take a 'domain' as argument so that low level sysdb functions know what domain you are asking to operate on.

This was partially done by embedding domain in the sysdb structure, but was the wrong way around because we have multiple domains in a sysdb so some code started creating artificial sysdb contexts in order to fill them with arbitrary domain members. This made the code very hard to read and follow.

Fields changed

owner: somebody => simo
status: new => assigned

This is an internal task only. No clone needed.

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta

The first part of refactoring landed in master:

git log --oneline e3ce042..f91e4aa

Second wave of refactor was commited to master:

git log --oneline 7a92ae1..3561e54

The third and last patchset was commited to master:

git log 2cbb879..4f118e3

resolution: => fixed
status: assigned => closed

Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: SSSD 1.10 beta

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2789

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.

Login to comment on this ticket.