fix: reject invalid any and local config#8133
Merged
yongtang merged 1 commit intoMay 31, 2026
Merged
Conversation
Signed-off-by: immanuwell <pchpr.00@list.ru>
yongtang
approved these changes
May 31, 2026
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.
1. Why is this pull request needed and what does it do?
anyandlocalwere accepting junk config instead of failing fast.Repro before this patch:
. { any example.org local { foo } }Both cases are reachable in normal startup config parsing, no weird setup needed. They should error, but they slipped through. This patch makes both plugins validate args/block content, and adds tests.
2. Which issues (if any) are related?
No direct issue found. Kinda the same lane as #8120, #8121, #8119 and #8128.
3. Which documentation changes (if any) need to be made?
None.
4. Does this introduce a backward incompatible change or deprecation?
Only for invalid config. Valid configs stay the same.