Learn more about these different git repos.
Other Git URLs
sssctl now shows all the domains:
sudo sssctl list-domains win.trust.test subdom.win.trust.test
There should be a flag (maybe together with some --verbose option) that identifies main domains versus subdomains.
Fields changed
cc: => pbrezina
milestone: NEEDS_TRIAGE => SSSD 1.14.1
rhbz: => todo
We need to release 1.14.1 soon, therefore moving to 1.14.2.
milestone: SSSD 1.14.1 => SSSD 1.14.2
owner: somebody => pcech
We should transition the 1.14 branch to the maintenance mode, moving to triage to discuss which milestone to fix this ticket at.
milestone: SSSD 1.14.2 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.16 beta
Metadata Update from @jhrozek: - Issue assigned to pcech - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @jstephen: - Issue assigned to jstephen (was: pcech)
Metadata Update from @jhrozek: - 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
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: Fixed - Issue set to the milestone: SSSD 1.15.3 (was: SSSD Future releases (no date set yet)) - 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/4098
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.