Patrick Brideau via FreeIPA-users wrote: > In my process of opening the bug in the SSSD github, I dug deeper and found > it is actually the expected behavior from the module: > > When called without argument, the function `sssdconfig.import_config()` > import only the `sssd.conf` > https://github.com/SSSD/sssd/blob/6958eecde6cd4f7c5b614677c218ea12e2fac53a/src/config/SSSDConfig/__init__.py.in#L1002 > > ```python > if not configfile: > #TODO: get this from a global setting > configfile = '@sysconfdir@/sssd/sssd.conf' > ``` > > I’m not sure if it would then be the responsibility of FreeIPA to import > config in the `conf.d` directory, instead of relying on the default config to > load entire config? If you don’t think so, I would be glad to open a bug > report on the SSSD side. Otherwise, maybe I should open with FreeIPA? > Thanks for your input Rob. >
I'm not sure what the answer is. I guess I'd have expected the python class to pull in all of its configuration in the same way that the main binary does. I'll ping the SSSD guys to see what's going on. rob rob -- _______________________________________________ FreeIPA-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
