On 22 Mar 2016, at 20:43, Simo Sorce <simo(a)redhat.com> wrote:
On Tue, 2016-03-22 at 15:15 +0100, Michal Židek wrote:
> On 03/22/2016 02:46 PM, Lukas Slebodnik wrote:
>> On (22/03/16 14:30), Michal Židek wrote:
>>> On 03/22/2016 12:29 PM, Michal Židek wrote:
>>>> Hi,
>>>>
>>>> I would like to write a patch that will
>>>> allow SSSD to use the config file merging
>>>> feature from libini. But first I would like
>>>> to ask developers for their opinions on how
>>>> this should be implemented.
>>>>
>>>> My idea was that it could work like this.
>>>>
>>>> The current /etc/sssd/sssd.conf would work
>>>> as usual.
>>>>
>>>> We would add new directory /etc/sssd/conf.d/
>>>> and its content would be following:
>>>> - README file that informs what the direcotory
>>>> is for.
>>>> - any number of files ending with .conf extension
>>>> that would contain additional configuration for
>>>> SSSD. These files would have higher prioriry
>>>> than the /etc/sssd/sssd.conf , meaning if
>>>> the same option is present in these files
>>>> it will override the /etc/sssd/sssd.conf
>>>> value.
What's the rational behind 'snippets vs main conf' makes snippet a
winner ?
The rationale is that the majority of systems tend to stick to a default, but there is one
odd server that needs to connect to a different server instead of using SRV discovery by
default. In that case, the admin would drop a snippet to the include directory with the
help of Puppet or Ansible or similar and change the resulting config file on that single
system w/o changing the authconfig/realmd/ipa-client-install that is usually set in the
kickstart.
(This is how I understand the use-case, feel free to come back with a counter-example..)