#2465 [RFE] Refactor SSSD to use configuration from ding-libs instead of DB
Closed: wontfix 4 years ago by pbrezina. Opened 9 years ago by dpal.

Instead of reading configuration and dumping it into DB SSSD monitor should read configuration and service it to the services. The services should get new configuration from SSSD on restart.

The scope of work
1. Make monitor send configuration to services on restart over SBUS
2. Make services read the configuration from the in memory config object rather than DB using ding-libs interpretation functions.
3. Make monitor reread configuration on SIGHUP and restart the services or force to reconnect so that new configuration can be propagated
4. Deprecate DB
5. Migrate from DB to pure ding-libs use

In future:

Include configration validation when it is ready from ding-libs


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

rhbz: => todo

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

This would make sense to do when we support the fallback config etc. but this won't happen in 1.14

milestone: SSSD 1.14 beta => SSSD 1.15 beta
sensitive: => 0

Metadata Update from @dpal:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/3507

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.

Metadata