Add IPv4/IPv6 preference support to ClientIpEnricher #55
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.
This PR implements IPv4/IPv6 preference functionality for the
ClientIpEnricher
to allow users to specify which IP version they want to log.Changes Made
New
IpVersionPreference
enumAdded enum with the following options:
None
(default): No preference - use whatever IP version is availablePreferIpv4
: Prefer IPv4 addresses when multiple are available, fallback to IPv6PreferIpv6
: Prefer IPv6 addresses when multiple are available, fallback to IPv4Ipv4Only
: Only log IPv4 addresses, ignore IPv6 addressesIpv6Only
: Only log IPv6 addresses, ignore IPv4 addressesEnhanced
ClientIpEnricher
AddressFamily
Extended Configuration API
Added new overload to support IP version preferences:
Example Usage
Testing
Documentation
Backward Compatibility
✅ No breaking changes - all existing code continues to work without modification
✅ Default behavior remains unchanged
✅ New functionality is opt-in only
Fixes #48.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.