feat: add RabbitPropsCustomizer and KafkaPropsCustomizer for flexible multi-domain configuration#169
Merged
juancgalvis merged 3 commits intoMay 12, 2026
Conversation
…omain and AsyncPropsDomain
… multi-domain configuration
Contributor
|
🎉 This PR is included in version 7.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Add support for RabbitPropsCustomizer and KafkaPropsCustomizer interfaces to enable
programmatic customization of domain properties at startup. Document the configuration approaches with examples
and guidance.
What's New
RabbitPropsCustomizer & KafkaPropsCustomizer
New feature: Customize async properties programmatically while keeping YAML configuration
Use case: Load connection credentials from secrets manager at startup, override YAML values
Constraint: At least one domain must be declared in YAML (if using customizer)
Benefit: Hybrid approach combines simplicity of YAML with runtime flexibility of code