manager: include config-validator.hpp always

There was an issue with

phosphor::led::validateConfigV1(systemLedMap);

being not included when using meson option

use-json

as false (yaml config), si

manager: include config-validator.hpp always

There was an issue with

phosphor::led::validateConfigV1(systemLedMap);

being not included when using meson option

use-json

as false (yaml config), since it was transitively included
by manager/json-parser.hpp

Directly including it should fix the issue.

Change-Id: I056cd524ff255e4409844f74bd7755ab5ee857d6
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...

config: error on invalid configuration

Since the default led priority is no longer 'Blink', the priority now
has to be explicitly defined when using either group priority or led
priority.

If a conf

config: error on invalid configuration

Since the default led priority is no longer 'Blink', the priority now
has to be explicitly defined when using either group priority or led
priority.

If a configuration does not define the priority, the configuration is
invalid and in the yaml case, phosphor-led-manager should fail to build,
in the json case, the process should exit due to the configuration
error.

The config validation has been extracted into it's own file and made
separate from json config parsing.

So every config will go through the same validation even if its been
created via yaml.

Change-Id: Ifda65942b0768d6c0d3b25076f7a1236b46b3d9f
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...