[SLING-10117] Support different configuration validation modes

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Feature Model API Regions Extension 1.2.0
• Component/s: Feature Model
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 02/Feb/21 10:44
• Updated: 02/Apr/21 11:27
• Resolved: 13/Feb/21 11:34

Description

If configuration rules for validating OSGi configuration are specified, these rules are strict - any violation will result in an error, failing the validation.
There are cases, where it is better to warn about invalid values instead. And when warning the invalid value might still be used or the invalid value is ignored.
This leads to the need of supporting different modes.
I think such a mode could be defined on different levels: global, per OSGi configuration, per OSGi configuration property where the latter overrides the former.
The default mode for global is strict.
We could support the following modes

• strict - if validation fails, issue an error
• lenient - if validation fails, issue a warning (but use the invalid value)
• silent - if validation fails, do not report and use the invalid value
• definitive - if validation fails, use the default value (if provided otherwise remove value) and issue a warning
• silent definitive - if validation fails, use the default value (if provided otherwise remove value) and do not issue a warning

Support of default values is part of SLING-10090