Add describe-routing sub-command to wolverine-diagnostics (#2468)#2487
Merged
jeremydmiller merged 2 commits intomainfrom Apr 9, 2026
Merged
Add describe-routing sub-command to wolverine-diagnostics (#2468)#2487jeremydmiller merged 2 commits intomainfrom
jeremydmiller merged 2 commits intomainfrom
Conversation
Adds a new `describe-routing` action to the existing `wolverine-diagnostics` CLI command, enabling inspection of message routing configuration without requiring database or transport connections. - `describe-routing <MessageType>` shows the local handler (if any), all routes with endpoint mode/outbox/serializer, route resolution method (local handler convention, explicit publish rule, transport routing convention, or [LocalQueue] attribute), and message-level envelope attributes - `describe-routing --all` shows the complete routing topology: routing conventions, message routing table (flagging unrouted types), listener topology, and sender topology - Fuzzy message type matching (full name, short name, alias, contains) - 8 new tests covering FindMessageType and routing smoke cases - Documentation added to docs/guide/command-line.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Fix premature class closing brace that left FindMessageType and describe-routing tests outside the class - Replace describe_routing_for_handled_message_finds_local_route with describe_routing_handled_message_is_known_to_handler_graph since RoutingFor() returns no routes in lightweight (WithinCodegenCommand) mode Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 11, 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
1 participant
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.
Summary
Implements #2468 — adds a
describe-routingaction to the existingwolverine-diagnosticsCLI command.wolverine-diagnostics describe-routing <MessageType>— inspect routing for a specific message type (fuzzy name matching: full name, short name, alias, or contains)wolverine-diagnostics describe-routing --all— show the complete routing topology for all known message typesOutput for a single type includes:
[LocalQueue]attribute)ModifyEnvelopeAttributesubclasses like[DeliverWithin])Output for
--allincludes:RouteWith()Runs in the same lightweight CLI mode as
codegen-preview— no database or transport connections required.Test plan
WolverineDiagnosticsCommandTests— 8 new tests coveringFindMessageType(exact, short, fuzzy, not-found) and smoke tests for routing (handled message gets local route, unhandled message gets no routes); all 13 tests passdotnet build src/Wolverine/Wolverine.csproj --framework net9.0docs/guide/command-line.md🤖 Generated with Claude Code