On 04/20/2016 12:49 PM, Jakub Hrozek wrote:
On Wed, Apr 20, 2016 at 12:04:23PM +0200, Michal Židek wrote:
> Hi,
>
> I just updated the design for the planned sss_confcheck tool.
> It can be found here:
>
https://fedorahosted.org/sssd/wiki/DesignDocs/ConfigCheckTool
>
> For convenience I paste it here as well:
>
>
> sss_confcheck tool
>
> Related ticket(s):
>
> https://fedorahosted.org/sssd/ticket/2269
>
> Problem statement
>
> There is no easy way to debug the SSSD configuration without having to look
> into the debug logs. Moreover the debug logs can be difficult to understand
> for people outside SSSD development team. Some common issues can be
> identified during static offline analysis of the config files. To find these
> issues soon we need a tool that performs this analysis and provides human
> readable report.
>
> Use cases
>
> - performing ad-hoc static analysis of the installed SSSD configuration
> - performing ad-hoc static analysis of SSSD configuration files retrieved
> from user with some SSSD problems
>
> Overview of the solution - sss_confcheck tool
>
> A new tool will be added to sss_* tools that will perform static analysis of
> SSSD configuration files. This tool can be run without any parameters in
> which case it will print a report to the standard output in the following or
> similar format:
>
> -----------------
> $ sss_confcheck
> Number of identified issues: 1
> [rule/allowed_nss_options]: Attribute 'foo' is not allowed in section
'nss'.
> Check for typos.
It might be nice to explicitly say what the validators will do in the
upcoming version (I know you linked the design document...)
Ok. I will add notes about version 1 to the bottom of the design page.
>
> Used configuration file:
> <Here will be the contents of sssd.conf file>
>
> Number of used configuration override snippets: 2
> List of configuration override snippets in order of priority (lowest
> priority first):
> snippet_name_1.conf
> snippet_name_2.conf
>
> Content of configuration override snippets:
> snippet_name_1.conf:
> <content of snippet_name_1.conf>
>
> snippet_name_2.conf:
> <content of snippet_name_2.conf>
Would it make sense to also print the resulting config file (merged with
snippets) ?
Yes, and I plan to do it, but I am not sure if it will go to
the first version, so I did not write it there. I will add it
to the design together with note that it may not be in the
first version.