Ankur Singla created SLING-13041:
------------------------------------
Summary: Inconsistent precedence behavior between legacy and new
configuration properties for bypass allowlist vs Bundles regexp
Key: SLING-13041
URL: https://issues.apache.org/jira/browse/SLING-13041
Project: Sling
Issue Type: Bug
Reporter: Ankur Singla
h3. Current Behavior
For bypass property
* The new config value is read first: config.allowlist_bypass()
* If the legacy property whitelist.bypass exists, it overwrites the new config
value
* Result: Legacy property takes precedence over the new property
For regexp property
* The new config value allowlist.bundles.regexp is checked
* If the new config is set (non-empty), the legacy property
whitelist.bundles.regexp is ignored with a warning
* Only if the new config is empty, it falls back to the legacy value
* Result: New property takes precedence over the legacy property
h3. Expected Behavior
Both properties should follow consistent precedence rules. The new
configuration property should take precedence over the deprecated legacy
property when both are configured. This is the correct semantic for backwards
compatibility: legacy properties should only be used as a fallback when the new
property is not explicitly set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
