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
Open
OAK-11628: Make WARN/ENABLE path restriction lenient and add feature toggle to warn by default#3118thomasmueller wants to merge 1 commit into
thomasmueller wants to merge 1 commit into
Conversation
…ction from DISABLED to WARN. WARN and ENABLE now ignore excludedPaths. (#3116)
Commit-Check ❌ |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



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.