Skip to content

OAK-11628: Make WARN/ENABLE path restriction lenient and add feature toggle to warn by default - #3118

Open
thomasmueller wants to merge 1 commit into
trunkfrom
OAK-11628
Open

OAK-11628: Make WARN/ENABLE path restriction lenient and add feature toggle to warn by default#3118
thomasmueller wants to merge 1 commit into
trunkfrom
OAK-11628

Conversation

@thomasmueller

Copy link
Copy Markdown
Member

Feature toggle to warn by default

Adds FT_OAK-11628 (pathRestrictionWarnByDefault), off by default, which raises the default StrictPathRestriction from DISABLE to WARN at runtime — so path-filter mismatch warnings can be switched on/off without a redeploy. No behavior change when off.

Lenient path filter check for WARN/ENABLE

WARN and ENABLE now use the same lenient check, ignoring excludedPaths, so they differ only in reaction (log vs. skip index). ⚠️ Intentional behavior change: under ENABLE, a query spanning an excluded subtree now uses the index instead of being rejected.

No SPI/API change, no OSGi version bump.

See OAK-11628.

…ction from DISABLED to WARN. WARN and ENABLE now ignore excludedPaths. (#3116)
@github-actions

Copy link
Copy Markdown

Commit-Check ❌

Commit rejected by Commit-Check.                                  
                                                                  
  (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)  
   / ._. \      / ._. \      / ._. \      / ._. \      / ._. \   
 __\( C )/__  __\( H )/__  __\( E )/__  __\( C )/__  __\( K )/__ 
(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)
   || E ||      || R ||      || R ||      || O ||      || R ||   
 _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._ 
(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)
 `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´ 
                                                                  
Commit rejected.                                                  
                                                                  
Type subject_max_length check failed ==> OAK-11628: Added feature toggle to set default of invalid path restriction from DISABLED to WARN. WARN and ENABLE now ignore excludedPaths. (#3116) 
Subject must be at most 120 characters
Suggest: Keep the subject concise (<= configured max)

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants