Learn more about these different git repos.
milestone: NEEDS_TRIAGE => SSSD 1.12.1
summary: RFE: Implement object caching on the bus => [RFE] Implement object caching on the bus
rhbz: => 0
changelog: => After reboot or startup, the cached objects would be immediatelly available on the bus for consumption.
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/DBusResponder
Mass-moving all tickets that didn't make 1.12.1 into 1.12.2
milestone: SSSD 1.12.1 => SSSD 1.12.2
We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3
milestone: SSSD 1.12.2 => SSSD 1.12.3
Aside from explicit caching stef suggested also using utmp in the same way accountService does. Also, when any object has a local override (in future) such as keyboard or picture, it will be cached as well.
mark: => 0
Notes from meeting with Stef:
the configuration should not be exported.
whenever a client connects, we make a note of it with the unique ID and keep track until NameOwner changed arrives.
I'm moving all D-Bus related tickets to 1.12.4. We are working on the interfaces in the 1.12 cycle, but as the interface won't be ready for 1.12.3 release anyway, it makes sense to realign all D-Bus tickets in 1.12.4
milestone: SSSD 1.12.3 => SSSD 1.12.4
The dbus patches are landing in 1.13 alpha for now to avoid breaking 1.12
milestone: SSSD 1.12.4 => SSSD 1.13 alpha
owner: somebody => pbrezina
patch: 0 => 1
status: new => assigned
resolution: => fixed
sensitive: => 0
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.13 alpha
to comment on this ticket.