Learn more about these different git repos.
Other Git URLs
Get and GetAll are on the list on review, we need to implement Set as well to make the property support complete, even though the current interface is read-only.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.12.1 priority: major => minor summary: RFE: Implement org.freedesktop.DBus.Properties.Set => [RFE] Implement org.freedesktop.DBus.Properties.Set
rhbz: => 0
changelog: => The DBus interface would allow properties not only to be read, but also set. 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
On a meeting we concluded that we don't need setters at all. It's easier to add modify methods instead to atomically modify several properties at once. Methods are also easier to work with polkit than setters.
We also don't need setters until we support local users.
mark: => 0
When an object the caller has no rights to read is requested, it should be just silently skipped rather than throwing an error.
We apparently don't need this until 1.13, moving to NEEDS_TRIAGE.
milestone: SSSD 1.12.3 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
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 testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
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)
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/3379
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.
Login to comment on this ticket.