Learn more about these different git repos.
Other Git URLs
Currently we have sss_debuglevel that is able to set the debug level of SSSD on runtime. We also have a request (ticket #1788) to extend sss_debuglevel to read the debug level and another request (ticket #385) to read the online or offline status.
Instead of several utilities each for one task, we could have one more integrated utility that would control the sssd state. The name proposed on a meeting was sssdctl.
The current tools like sss_debuglevel would become symlinks to the new tool.
Fields changed
type: defect => enhancement
milestone: NEEDS_TRIAGE => SSSD 1.11 beta summary: RFE: create a generic sssdctl utility => [RFE] create a generic sssdctl utility
Related #1788
rhbz: => todo
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=879333 (RHEL RFE)
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=879333 879333]
changelog: => keywords: => Status review: => 0
mark: => 1
owner: somebody => preichl
This is a superset of #1788, not sure we can implement the whole sssdctl in time, but let's start and see how far we get..
Downstream no longer requires this RFE. Moving to backlog.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
milestone: SSSD 1.13 backlog => SSSD 1.14 alpha priority: major => blocker sensitive: => 0
In Alpha we will only implement the API, the utility will be part of the Beta release.
milestone: SSSD 1.14 alpha => SSSD 1.14 beta
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/sssctl
owner: preichl => pbrezina
Pavel sent me his branch for review, marking as has-patch.
patch: 0 => 1
Fixed as part of the sssctl patchset:
resolution: => fixed status: new => closed
Metadata Update from @jhrozek: - Issue assigned to pbrezina - Issue set to the milestone: SSSD 1.14 beta
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/2842
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.