feat: make plugin FQN configs optional with strict-or-graceful loading#237
Merged
popduke merged 2 commits intoapache:mainfrom Mar 30, 2026
Merged
feat: make plugin FQN configs optional with strict-or-graceful loading#237popduke merged 2 commits intoapache:mainfrom
popduke merged 2 commits intoapache:mainfrom
Conversation
…loading Make authProviderFQN, resourceThrottlerFQN, and settingProviderFQN in standalone.yml optional to improve local dev/test ergonomics. - If a *FQN field is explicitly set, treat it as a hard requirement: BifroMQ will fail fast on startup if the plugin class is missing or fails to initialize. - If the field is omitted, apply auto-selection logic: 1. Discover all registered custom plugins for the extension point. 2. Sort by plugin key (byte-wise alphabetical) and pick the first. 3. Fall back to built-in default only if no custom plugins exist. This provides a clear contract for production (explicit = strict) while keeping local development simple and low-friction. Fixes apache#236
liaodn
changed the title
popduke
reviewed
Mar 30, 2026
Signed-off-by: liaodongnian <361485583@qq.com>
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
2 participants
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.
Make authProviderFQN, resourceThrottlerFQN, and settingProviderFQN in standalone.yml optional to improve local dev/test ergonomics.
This provides a clear contract for production (explicit = strict) while keeping local development simple and low-friction.
Fixes #236