Learn more about these different git repos.
Other Git URLs
Continuation of the systemtap effort, notes from Jakub below:
"the handlers of the respective providers could be next so that the admin could observe not only what requests were flowing, but also what the requests were actually for (e.g. that the request was for a group called XXX, then the admin will know, if the request was taking too long that they might want to suppress group members or restrict nesting..)"
Metadata Update from @jstephen: - Issue assigned to jstephen
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.4
PR: https://github.com/SSSD/sssd/pull/261
Metadata Update from @jhrozek: - Issue tagged with: PR
Metadata Update from @jhrozek: - Issue priority set to: major - Issue tagged with: RFE
Removing the PR keyword because I got confused with PR for https://pagure.io/SSSD/sssd/issue/3061 and realized my mistake only when reviewing https://github.com/SSSD/sssd/pull/261
I also think we shouldn't force this ticket into 1.15.4 -- if it makes it, fine, but for now, I'm moving the ticket into 1.16.0
Metadata Update from @jhrozek: - Issue untagged with: PR
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
Metadata Update from @jhrozek: - Issue tagged with: postpone-to-2-0
Metadata Update from @jhrozek: - Issue untagged with: postpone-to-2-0 - Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)
Metadata Update from @jhrozek: - Issue priority set to: minor (was: major)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Metadata Update from @thalman: - 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/4443
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.