Learn more about these different git repos.
Other Git URLs
This is a requirement that is similar to #1165 & #1264 however it is a bit more simple.
It replaces #1165 and steps into area of #1264. As a result ticket #1165 will be closed as won't fix and ticket #1264 will be put into Deferred milestone.
SSSD should not expect that domains are defined in one file. Rather expect that some domains can be defined in main sssd.conf and then additional domains can be read from files defined in a special directory. It will be expected that files in the directory all define separate domains and do not step on each other. Otherwise there would be an error. Whether the domains defined in the main sssd.conf can be overwritten or not should be an option.
keywords: => localaccounts
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=790113 790113]
cc: => Michael.Gliwinski@henderson-group.com
mark: => 1
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the 1.13 release to 1.14
milestone: SSSD 1.13 backlog => SSSD 1.14 beta
The ding-libs changes are mostly done, so the SSSD part should be quite easy - making it a stretch RFE for 1.13.
milestone: SSSD 1.14 beta => SSSD 1.13 backlog
cc: Michael.Gliwinski@henderson-group.com => Michael.Gliwinski@henderson-group.com, firstname.lastname@example.org
sensitive: => 0
IIRC ding-libs should support this functionality and we need it for the secrets as a service work.
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/ding-libs/INIConfigMerge
owner: somebody => mzidek
patch: 0 => 1
Please note that this functionality depends on the latest ding-libs release.
resolution: => fixed
status: new => closed
Metadata Update from @dpal:
- Issue assigned to mzidek
- 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:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.